Skip to main content


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

Security of access roles

Updated on July 1, 2021

An access role rule defines a name for a role, and represents a set of capabilities. As Access roles are a fundamental part of the security in Pega Platform, there are a number of rules that affect access roles.

Explanation of access roles

The access roles are described in text below, however, a summary image is shown below.

Each authorized user has an Operator ID.

The Operator ID contains at least one Access Group. An Operator ID must have at least one access group, but can have multiple access groups.

The Access Group contains at least one Role. An Access Group must contain at least one role, but can have multiple roles.

The Roles contain an Access Role name. This Access Role name makes a call to the Rule-Access-role-Obj, which are also called RARO. The RARO is contains Privileges.

The Access Role name is assigned based on the classes in the application. For each class, there can be an Access of role to Object rule, which assigns the privileges to the role for that class.

The privileges shown in the image below are explicit privileges and are assigned on the rules.

The privilege can also be seen on the Security tab of the activity.

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