Org Structure
Load the standard setup and sample data, then shape the organisation tree that scopes who sees which assets.
Overview
You do not have to configure anything to start. The first time the module is used it loads a standard setup by itself: an asset class tree with typed fields, a naming scheme, the status workflow, commissioning checklists, failure codes, SLA policies, maintenance teams, inspection templates and a statutory compliance register.
Org Structure is where you review and extend that setup. It also holds the organisation tree (group, country, company, branch, site) that scopes visibility, and two buttons that save a lot of time on a new tenant: Load standard setup and Load starter data.
When to use org structure
- You are setting up Assets for the first time and want a working baseline in one click.
- You want sample assets, sites and classes to explore the module or to train people.
- You need to add a country, company, branch or site node so assets and users can be scoped to it.
Prerequisites
- The Assets module installed from the App Store
- A user with the owner role or the assets.org.manage permission
Step by step
Field reference
| Field | Description | Required | Data type | Business meaning |
|---|---|---|---|---|
| Node type | Level in the organisation tree. | Yes | Group, country, company, branch or site | Determines how visibility grants cascade. |
| Code | Short unique code of the node. | Yes | Text | Used in the asset naming scheme, for example the site part of KE-NRB-PMP-001. |
| Name | Display name. | Yes | Text | Shown in filters, locations and reports. |
| Parent | The node it sits under. | Yes (except the top node) | Org node | Roles granted on a node apply to everything beneath it. |
Permissions
These permission keys control access (granted to roles in Administration → Roles & Permissions):
- assets.org.manage
- assets.class.manage
- assets.naming.manage
- assets.status.manage
Automation
- Changes on this screen are written to the asset audit trail and the asset timeline.