Administration owns structural Axis editing. The resulting map is readable in Standards under Map, so employees can follow responsibilities without entering the administrator control plane.
Every organization starts with one Axis, Whole organization, so Responsibility opens straight onto its Role tree. Add another Axis from the page menu only when the organization is sliced more than one way, such as by function and by geography.
- 1
Build the Role tree
Start with broad mandates and add narrower responsibility nodes beneath them.
- 2
Assign holders
Connect the stable Role to the people accountable now.
- 3
Review governed content
Check ownership and visibility that depend on moved or renamed Roles.
Model responsibility, not access
Do not create Roles as security groups or mirror every access role.
Names outlive holders
Name the responsibility, not the current holder. Organizational changes can replace people without forcing every Standard and visibility rule to adopt a new concept.
Change structure carefully
Moving a Role can affect inherited ownership and the interpretation of Role-scoped visibility. Review dependent Standards before making a large reorganization.
Keep the public map legible
The Map view under Standards is the everyday face of this structure. A technically complete hierarchy that employees cannot understand has failed its primary job.