Skip to main content
Version: 7.3

Roles

Introduction​

The Roles page in contentACCESS Central Administration allows administrators to manage the roles that define the permissions assigned to contentACCESS users throughout the system.

Every contentACCESS user has at least one assigned role, and a user can have multiple roles assigned simultaneously. Roles determine what a user is permitted to configure and which data they can access, both in Central Administration and in contentACCESS Portal.

contentACCESS provides a set of default, system-level roles, but administrators can also create new roles with specific, customized permissions.

Default system roles​

contentACCESS includes default (system-level) roles. These roles are visible to all tenants, cannot be edited or deleted, and are displayed with a distinct color in the user interface.

The default roles are:

  • System administrator: Has permissions to configure everything in contentACCESS Central Administration and has access to all processed data in contentACCESS Portal.
  • Tenant administrator: Can configure their own tenant in Central Administration and can see all processed data belonging to that tenant.
  • Standard user: A client application user with specific, limited permissions. Because of this, a standard user must be associated with specific contentACCESS objects, such as an archived mailbox. This role is typically created for end users who need access to their assigned archives in contentACCESS Portal.
  • Repository editor: Has permissions to create, edit, and delete repository items, such as databases and storages.
  • Configuration administrator: Has the same permissions as the system administrator, with one exception — no access to archived data, and therefore no access to contentACCESS Portal.
  • Junior configuration administrator: Has the same permissions as the configuration administrator, with one exception — no access to assign user roles.
  • Tenant configuration administrator: Has the same permissions as the tenant administrator, with one exception — no access to archived data, and therefore no access to contentACCESS Portal.
  • Junior tenant configuration administrator: Has the same permissions as the tenant configuration administrator, with one exception — no access to assign user roles.
info

Note: Default roles are read-only. To assign custom permission sets, create a new role instead of modifying a default one.