Pega Platform provides several standard access role name rules. These role names are referenced in standard Access of Role to Object rules to control the classes that users with these access role names can see and update.
|Allows access to use automated unit testing.
|For background requestors, including agents.
|Allows unauthenticated access with minimal access.
|Allows unauthenticated access with more capabilities, including the ability to open and update the user's own work items.
|Allows a user to use the Pega API.
|Allows a developer to have full capabilities.
|Allows an administrator to have full use of the Admin Studio portal (pxAdminStudio). There is also a standard access group named SysOpsAdministrator.
|Allows a user to have read-only use of the Admin Studio portal (pxAdminStudio). There is also a standard access group named SysOpsObserver.
|Application user with limited capabilities. Cannot perform assignments on worklists other than the user's own worklist. Uses Get Most Urgent to obtain the next assignment.
|For users with broader capabilities. Can open any work object in the application. Can perform assignments only on the user's own worklists.
|Allows a work manager to have full capabilities, including viewing and updating delegated rules.
|For a business analyst or a system architect who defines processes, classes, and properties (Data Model category), and can develop activities.
|For a process architect who focuses on flows and other rules in the Process and User Interface categories.
|For collaborators who participate in development of the application as editors. Can view and change application assets.
|For collaborators who participate in development of the application as reviewers. Can view application assets, but cannot change them.