Skip to content
SanShivaSHELL ELOS Docs
Browse the documentation

Permissions reference

For administrators, security and compliance 4 min read

Every permission in ELOS, what it allows, and which ones are sensitive.

Roles are built from these permissions. The server checks them on every request; the portal only shows what your role allows. Sensitive permissions are flagged in the role editor.

PermissionKeyAllowsSensitive
Read tenant datareadView services, people, knowledge and onboardingNo
View audit & complianceaudit.viewThe audit log, access reviews and compliance evidenceNo
Author docsdocs.writeCreate, lint and publish docsNo
Request accessaccess.requestRaise access requests for approvalNo
Edit service catalogservice.editUpdate service metadata and assign ownersNo
Run access reviewsreviews.manageStart reviews and decide accessNo
Approve accessaccess.approveApprove or deny access requests, which issues grantsYes
Manage peoplepeople.manageRegister joiners, start onboarding, change roles and offboardYes
Manage integrationsintegrations.manageConnect and disconnect tools, and sync themYes
Manage settingssettings.manageEdit workspace settings: retention, policy and compliance scopeYes
Manage rolesroles.manageCreate and edit roles and service accounts. Reserved to administrators; can't be placed in a custom role.Yes
Use Ask ELOSai.useAsk the assistant for grounded, cited answersNo
Use AI agentsai.agentsAnswers that use several AI agents; agents only reach data the role can already seeNo
Let AI draft actionsai.actionsLet the assistant propose actions, such as an access request. Proposals go to approval and still need the action's own permission.Yes

Rules

  • You can only grant permissions you hold, in a role or by assigning a role to someone.
  • Platform Admin is fixed, so there's always a break-glass administrator.
  • A custom role's read scope limits what it sees everywhere, including in Ask ELOS.

What's next