Organization, Identity, Access, and Governance
Administration — Organization
On this page
Navigation: Administration → Organization
Primary audience: organization administrators, data owners, governance owners, and delegated business administrators
Purpose
Organization defines the business structure and ownership context used throughout the workspace. It manages workspaces, regions, business units, customers, accounts, projects, products, services, inheritance, and required object ownership.
Scope controls and indicators
Workspace selects the configured workspace or environment view. Business Unit narrows the hierarchy. Object Type filters units, accounts, projects, products, or services. Ownership filters complete or missing assignments.
Business Units, Customer Accounts, and Projects show configured counts and active subsets. Ownership Gaps identifies objects missing a required owner or steward.
Organization model
The hierarchy shows parent and child units such as Delivery, Sales, Engineering, Architecture, Legal, and regional units. Selecting a node opens owner, users, groups, connectors, retention inheritance, eligible purposes, restricted-area access, and data-residency policy.
The inheritance view explains which settings come from the workspace or parent unit and which are overridden locally.
Supporting analysis
Object distribution shows where customer, delivery, corporate, and regional objects reside. Ownership gaps lists the affected object, missing role, impact, and required assignment. Organization actions provides ownership and structure-review work.
Actions
- Edit structure adds, moves, renames, archives, or changes a business unit under approval rules.
- Assign an owner, data steward, policy owner, or other required role.
- Review or override permitted inheritance.
- Create or link customer, account, project, product, or service context.
- Add a unit and preview affected access, policies, and navigation before approval.
Recommended procedure
Maintain a stable hierarchy based on accountability rather than temporary reporting preferences. Resolve ownership gaps before enabling business processing. Preview inheritance and permission effects before moving an object or unit.
States and limitations
Archiving a unit does not delete historical records. Structural changes can affect scope, access, reporting, retention, and assignments and therefore require an impact preview. Production changes remain traceable and reversible through the administrative change process.