NetNada

How to set up your organisational structure

Last updated: 10 April 2026

Org Structure Nodes Node Map Admin Panel

Organisation Structure Walkthrough

Your organisational structure defines how your business is represented in NetNada — its facilities, regions, and legal entities. Setting this up is one of the first things you should do, as everything else (emissions boundaries, tasks, and dashboards) depends on it. Navigate to Admin > Nodes to get started.

In this article, you'll learn how to:

  • Add individual nodes (facilities, regions, businesses)
  • Build a parent-child hierarchy
  • Bulk upload locations from a registry or spreadsheet
  • Use the Node Map to review and validate your structure
Not sure what nodes are or which type to use? Read Understanding nodes and organisational structure first.

Adding a Node

1

Navigate to Admin > Nodes

Open the Node Table tab to see your existing nodes in a list view.
2

Click + Add Node

This opens the node creation form.
3

Enter the node name

Use a clear, descriptive name — e.g., "Sydney CBD Office" or "Australia Region". Use consistent naming conventions across all nodes.
4

Select the node type

Choose from Business, Region, Facility, Project, or Product. The type determines which emission categories are available.
5

Set the country and state

This is critical for facilities — emission factors for electricity and other location-dependent categories are selected based on this. Always set it for any node with physical operations.
6

Choose a parent node

Select the node this sits under in your hierarchy. For example, "Sydney CBD Office" might sit under "Australia" or "New South Wales". Select "None" for a top-level entity.
7

Add a node reference (optional)

If your ERP or accounting system uses location codes, enter the code here. This allows NetNada to automatically route bulk data uploads to the correct node.
8

Save

Click Add Node to save. The node will appear in both the Node Table and Node Map.

Building Your Hierarchy

A well-structured hierarchy makes data collection, reporting, and auditing significantly easier. Start from the top and work down:

  1. Business node — Your top-level legal entity (e.g., "ABC Company Pty Ltd")
  2. Region nodes — Geographical groupings (e.g., "Australia", "New Zealand", or "APAC")
  3. Facility nodes — Physical locations (e.g., "Sydney CBD Office", "Melbourne Warehouse")

There is no limit on hierarchy depth, but 3-4 levels is typical. The structure should reflect how your organisation actually operates — not how you wish it was structured.

Nodes without a parent (orphaned nodes) will not roll up into your organisation's totals. Check the Node Map for disconnected nodes after setup.

Bulk Uploading Nodes

Organisations with many locations (e.g., 70+ sites) don't need to add nodes one by one. If you already have a location registry or asset registry, you can upload it directly.

1

Navigate to Admin > Nodes

Click the Bulk Upload button.
2

Prepare your file

Use a spreadsheet with columns for node name, type, parent node, country, and state. Node references are optional but recommended.
3

Upload and review

Upload the file. NetNada will process it and create nodes automatically. Review the results in the Node Table to confirm everything was imported correctly.

Reviewing with the Node Map

After adding your nodes, switch to the Node Map tab to see the visual hierarchy. Use it to:

  • Verify parent-child relationships are correct
  • Spot orphaned nodes that aren't connected to the hierarchy
  • Switch between vertical and horizontal layouts
  • Share the visual with your auditor or internal stakeholders

FAQ

Can I edit a node after creating it?
Yes. Click the three dots menu (...) on any node in the Node Table to edit its name, type, parent, location, or reference code.
Can I delete a node?
Nodes linked to active emissions boundaries cannot be deleted. Remove the boundary link first, then delete the node. Nodes with uploaded data should be handled carefully — reassign the data before deleting.
What if I have duplicate nodes causing double-counting?
Review your Node Table for duplicates. Reassign any data from the duplicate to the correct node, then delete the duplicate.
Should I set up nodes before or during the emissions boundary process?
Either works. You can set up nodes first and then configure your boundary, or create nodes as you go through the boundary setup. We recommend setting up your structure first for a smoother experience.
What format does the bulk upload expect?
A spreadsheet (Excel or CSV) with columns for name, type, parent, country, and state. Download the template from the bulk upload page for the exact format.

Related Articles

How to set up your emissions boundary Getting started with NetNada: Your first steps Understanding nodes and organisational structure
Jump to section