Roles and Access
Platform
Text size
Roles and Access
Aiden 2.0 organizes access across two levels: the Organization (Tenant) and the Workspace. Each level has an admin role and a non-admin role, with a clear hierarchy from Admin down to Workspace User.
Role Hierarchy
| Role | Level | What they can do |
|---|---|---|
| Admin | Organization |
|
| Workspace Admin | Workspace |
|
| Workspace User | Workspace |
|
Who Can Access Settings
- An Admin invites users at the organization level and assigns them to workspaces.
- A Workspace Admin invites other Workspace Admins or Workspace Users to the workspaces they administer. A Workspace Admin cannot grant Admin access.
| Feature / Settings | Admin | Workspace Admin | Workspace User |
|---|---|---|---|
| Workspace Settings | ✅ | ✅ | ❌ |
| Org Settings (integrations, members, workspaces) | ✅ | ❌ | ❌ |
| Apps (Aiden Chat, DevOps, SRE including Discovery, Alerts, Investigations) | ✅ | ✅ | ✅ |
For details on organization configuration, see Organization Settings. For what a Workspace Admin can configure, see Workspace Settings.
Role Names
Workspace User is the name for the non-admin workspace role throughout Aiden. If you invite members through the API, the underlying role names are admin, workspace-admin, and user — where user is the Workspace User role.
note
Changes to a member's role or workspace membership can take up to a minute to apply to agent actions and policy checks that are already in flight.