Org admin overview
What organization admins control and how the permission hierarchy works.
The permission hierarchy
There are three layers of administrative control. Each layer can restrict what the layer below it does — but can never grant more than what it has been given itself.
| Layer | Who | Where |
|---|---|---|
| Org Admin | IT admin at your company | Organization settings |
| Team Admin | Manager or team lead | Team settings → Admin tab |
| End User | Employees and users | Everything else |
As an org admin, you set the rules for everyone in your organization. Team admins can tighten things further for their teams, but they cannot exceed the limits you set.
What org admins control
From Organization settings, you control:
- Skills access — which skills users can browse, install, and create
- Connections — which external services (Google, Microsoft) users can connect, plus company-wide Slack/Teams setup
- SSO & SCIM — single sign-on and automated user provisioning
- Audit log — full history of admin actions, configurable delivery to S3
- Sharing policy — whether users can share tasks or contacts outside the org
How settings resolve
When the platform evaluates what a user can do, it walks the hierarchy from bottom up:
- Does the user's team have an explicit override? Use it.
- Does the org have a setting? Use it.
- Fall back to the developer's platform default.
Team admins can set each toggle to Inherit (take the org value), On, or Off. They cannot set something to On if the org has it Off.
Who is an org admin?
Org admin access is granted by the developer when provisioning your organization, or by another org admin via Organization → Members. Org admins see the Organization settings tab in the sidebar. Regular users do not.