Skip to main content

Access and responsibilities

A role's name does not override authorization checks. Review the actual permissions, the target account's protection and the active tenant before changing access.

Responsibility map​

IdentityIntended workBoundary
Ordinary staffBusiness operations through assigned rolesNo administration merely because they can sign in
Tenant access administratorUsers, roles and grants where authorisedCannot delegate arbitrary missing permissions
Tenant owner / SUPER_ADMINBounded delegation and protected tenant setupSeparate from a platform operator; owner identity and membership are protected
Platform OPERATORTenants, entitlements, invitations and recoveryUses separate /operator sign-in
Platform AUDITORRead tenant and platform audit informationCannot perform operator mutations

Permission checklist​

TaskRelevant permission families
Discover users / roles / permissionsuser.view, role.view, permission.view
Maintain ordinary usersuser.create, user.update, user.delete
Maintain rolesrole.create, role.update, role.delete
Work on administrator targetsCorresponding admin.view, admin.create, admin.update, admin.delete, admin.lock or admin.unlock
Delegate approved permissions the actor does not holdtenant.permission.grant, plus the ordinary endpoint operation authority
Maintain operating-unit grantsuser.business-unit.assign; removal has a separate user.business-unit.remove API authority
Read business unitsbusiness-unit.view; active assignment choices also accept user.business-unit.assign
Configure capabilitiestenant.module.view/manage and tenant.feature.view/manage
View/manage Appearancetenant.module.view or tenant.module.manage for entry; management requires the manage authority

The table identifies relevant authorities, not a promise that one code alone opens an entire workflow. Discovery lists, target protections, tenant capabilities and scope can add checks. Server-provided allowed actions determine which edit and assignment buttons appear.

Example: Ali can edit ordinary users but cannot see Sara in the user list without administrator-view authority. Searching again does not remove that restriction. A missing user is not evidence that the owner account was deleted.

Never use another tenant's account ID to work around a missing selection. Roles, users, units and configuration must belong to the active tenant. The backend remains authoritative even when an old browser tab still shows a button.