Skip to main content
For the list of built-in roles, see Built-in User Roles. xorlab defines the concepts of Roles, Permissions and Scopes:
  • A Permission denotes a specific action bound to a specific Scope. Example: Releasing an email from the quarantine.
  • A Scope limits a permission to a specific context. Example: Releasing an email is only allowed for a specific tenant.
  • A Role is a set of Scopes with Permissions. If needed, Roles can be arbitrarily composed and assigned to users.
Only roles can be assigned to users.

Create a new role

  1. Open the file xcc.yml in the Expert Editor.
  2. Add the name and permissions of the new role to roleToPermissionMappings. You can find all permissions below at Permissions-role matrix. Optionally, you can restrict the scope of permissions as shown in Set the permission scope
    xcc.yml
Hint: You can query your current permissions as described here.

Set the permission scope

Optional: you can restrict the permission scope with the following syntax. If you omit the scope, the permission will have global scope.
Examples: When you finish editing roleToPermissionMappings in xcc.yml, click Publish. The role mapping becomes active within about one minute.

Permissions-role matrix

This table shows whether a specific built-in role has a Permission or not and if so with what Scope.
  • Table entry global means that the role has unrestricted access for a specific permission.
  • Table entry tenant:primary means that the role has access for a specific permission but only within the bounds of the current user’s tenant.
  • A missing table entry indicates that the role does not have that permission at all.