Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Standard access roles

Updated on July 1, 2021

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.

NameDescription
PegaRULES:AutoTestAllows access to use automated unit testing.
PegaRULES:BatchFor background requestors, including agents.
PegaRULES:GuestAllows unauthenticated access with minimal access.
PegaRULES:Guest-MaximumAllows unauthenticated access with more capabilities, including the ability to open and update the user's own work items.
PegaRULES:PegaAPIAllows a user to use the Pega API.
PegaRULES:SysAdm4Allows a developer to have full capabilities.
PegaRULES:SysOpsAdministratorAllows an administrator to have full use of the Admin Studio portal (pxAdminStudio). There is also a standard access group named SysOpsAdministrator.
PegaRULES:SysOpsObserverAllows a user to have read-only use of the Admin Studio portal (pxAdminStudio). There is also a standard access group named SysOpsObserver.
PegaRULES:User1 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.
PegaRULES:User4For users with broader capabilities. Can open any work object in the application. Can perform assignments only on the user's own worklists.
PegaRULES:WorkMgr4Allows a work manager to have full capabilities, including viewing and updating delegated rules.
PegaRULES:SysArch4For a business analyst or a system architect who defines processes, classes, and properties (Data Model category), and can develop activities.
PegaRULES:ProArch4For a process architect who focuses on flows and other rules in the Process and User Interface categories.
PegaRULES:EditorCollaboratorFor collaborators who participate in development of the application as editors. Can view and change application assets.
PegaRULES:ViewerCollaboratorFor collaborators who participate in development of the application as reviewers. Can view application assets, but cannot change them.
  • Previous topic Granting portal access to an access group
  • Next topic Updating access groups by submitting a request to an active instance

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us