Companies and business units
Two levels of structure, what the company boundary actually separates, and what the unit switcher does to every list.
There are two levels of organizational structure, both drawn as a chart under Platform → Org Structure.
| Level | What it is |
|---|---|
| Company | A legal entity, optionally grouped under a parent. Data is fully segregated between companies. |
| Unit | The tree inside a company: business unit, division, department, cost centre, site — to any depth. |
Every org-scoped table carries the unit, so master data and transactions alike are attributed to a place in the tree.
What the switcher does
- Selecting a company scopes everything to that legal entity. You may only choose companies you are entitled to; administrators reach all of them.
- Selecting a unit narrows every list to that unit and everything beneath it. Pick a business unit and you see all of its departments’ work.
- New records default to the selected unit, and the unit stays editable on the record.
The company boundary — including the parts that are easy to miss
| How it is scoped | |
|---|---|
| Roles | Each company has its own role set and its own administrator. A role can only be assigned within its own company. |
| Document numbering | A counter per company per document type. Every company’s first purchase order is PO-000001. |
| Document numbers | Unique per company, not globally. |
| Configuration lists | Per company. One company’s leave types are not another’s. |
| Audit log and event feed | Per company. The dashboard reads only the active company’s. |
Structural rules are enforced on the server: a unit cannot be moved inside its own subtree, a company root cannot be deleted, and a unit still holding records or child units refuses deletion rather than silently orphaning them.
A company created at runtime is provisioned with roles, number ranges and configuration values immediately — it is usable without a restart.