dotCMS provides several built-in system roles which serve specific functions within dotCMS, and which provide common roles and functions. System roles are pre-defined in all dotCMS installations and can not be removed.
Some system roles may be assigned to specific user accounts to perform certain types of actions. Other system roles are special roles which allow you to grant certain users permissions to access specific objects.
Current System Roles
The following system roles are currently supported in dotCMS. For more information on each role, please select the role from the list below.
|System Role||Assigned To||Description|
|CMS Administrator||Users||Allows access to all portlets and objects regardless of the permissions on those objects.|
|CMS Anonymous||Objects||Allows an object to be accessed by anyone, even regular site users who are not logged into the dotCMS back-end.|
|CMS Owner||Objects||The original creator of an object.|
|Current User||Objects||Used in Workflows to assign an object to the user who is drafting/publishing the dotCMS asset.|
|LDAP User||NONE||Assigned through LDAP integration ONLY.|
|LoggedIn Site User||Objects||Restricts access to users logged into the dotCMS back-end.|
|Login As||Users||Allows an administrator to login as another user, to configure or test performance of user accounts.|
|Scripting User||Users||Enables the user to run special scripts and execute SQL select statements inside front end/dotCMS widget code.|
Legacy System Roles
In addition, dotCMS maintains a number of legacy system roles for backward compatibility. For more information please see the Legacy System Roles documentation.