Create and maintain organizational units and memberships
Model departments, teams, and business units with clear ownership.
Table of Contents
Org units group people for access and work assignment. Membership can be maintained manually or derived from a rule. Because membership affects downstream audiences and access, define ownership and review changes carefully.
Before you begin
- You need permission to create or edit org units; dynamic membership rules have a separate capability.
- Agree the hierarchy, unit owners, and the authoritative person attributes used by any membership rule.
Steps
- Open Org units. Select What are org units? for the in-product overview, then New org unit.
- Enter a Name and Description. Choose the Level, Parent, and Owner. Business Units sit at the top; Departments and Teams can stand alone or nest under a parent.
- Select Create unit. Open the resulting unit to maintain its details and membership using the controls available to your role.
- For static membership, maintain the explicit list of people. For rule-based membership, define the intended attribute rule and review the expected population and any owner approval requirement.
- Allow for the rule synchronization cycle. Rule-managed units re-sync overnight rather than immediately when someone’s profile changes.
- Before changing a unit’s parent, owner, or membership model, review its use in campaign audiences, access assignments, and other dependent configuration.

Expected result
The unit has a clear place in the hierarchy, an owner, and an intentional membership source.
Verify the configuration
- Confirm the unit appears at the expected level and parent.
- Check known members and a person who should be excluded.
- For rule-managed units, verify the population after the scheduled re-sync and check Membership approvals if a rule change is pending.
Troubleshooting and maintenance
- A profile edit does not imply immediate rule-membership recalculation.
- Returning a rule-managed unit to manual membership keeps its current members; review that retained population.
- When selecting an org unit in access-rule audiences, its sub-units are included. Review each feature’s audience summary before relying on hierarchy behavior.

Review downstream ownership and access
For the owner's pending-rule decision queue, use Review organizational membership approvals. Membership approvals handles organizational membership-rule changes, not disclosure approval decisions.
Before changing a unit used in review or access, inspect Configure approver groups and routing tables and Manage roles, capabilities, and access policies. Verify both intended included people and a person who should remain excluded after the synchronization cycle.