Admin
Manage users within your organization and configure roles and permissions using tenant-scoped RBAC (Role-Based Access Control).
Scope: Workspace-scoped — requires organization administrator permissions and valid credentials for that workspace.
Roles are scoped to different levels:
Customization Tier: SYSTEM_FIXED (cannot be changed)
Roles follow a hierarchy:
Customization Tier: TEMPLATED_OVERRIDE (pack provides role templates, you can create custom roles)
Roles can be assigned at:
Users can have multiple roles:
Industry packs provide role templates:
Healthcare Pack:
Retail Pack:
Manufacturing Pack:
Customization Tier: TEMPLATED_OVERRIDE (pack provides templates, you can create custom roles)
Permissions are organized by category:
The People directory manages:
Assign roles at organization level:
Assign roles at location level:
Combine organization and location roles:
Problem: Assigning SYSTEM roles or not understanding TENANT vs LOCATION scopes.
Solution: Understand role scopes:
How to avoid: Review role scope documentation before assigning roles.
Problem: Giving users more permissions than needed.
Solution: Follow principle of least privilege:
How to avoid: Make permission review part of user onboarding.
Problem: Using only organization-wide roles when location roles would be better.
Solution: Use location roles when:
How to avoid: Consider location roles during role design.
Problem: Creating custom roles without documenting purpose and permissions.
Solution: Document all custom roles:
How to avoid: Make documentation part of role creation workflow.
Symptoms: User has role but can't access expected features.
Possible causes:
Steps to resolve:
Symptoms: Role or permission changes not reflected for user.
Possible causes:
Steps to resolve:
Symptoms: Unable to create custom role or assign permissions.
Possible causes:
Steps to resolve:
Managing users and roles requires tenant admin permissions. Role changes affect user access immediately. All roles and permissions are scoped to your organization.
