Skip to main content


Defining the authorization scheme

6 Topics

1 hr

Visible to all users
Advanced Pega Platform 8.3.1 English
This content has been updated. Click here to continue your progress on the latest version.

In most cases, you want to restrict authenticated users from accessing every part of an application. You can implement authorization features that ensure users can access only the user interfaces and data that they are authorized to access. The Pega Platform provides a complementary set of access control features called Role-based access control and Attribute-based access control.

Another access control capability in Pega is Client-based access control (CBAC). This is more focused on tracking and processing requests to view, update or remove personal Customer data held across your Pega applications, such as that required by EU GDPR (and similar) regulations. In itself, it doesn’t influence the authorization considerations for lead system architects when designing a Pega application, and is not discussed further in this module.

After completing this module, you should be able to:

Compare role and attribute based access control
Identify and configure roles and access groups for an application
Determine the appropriate authorization model for a given use case
Determine the rule security mode

Available in the following mission:

Lead System Architect

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

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice