Skip to main content

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

Security configuration components

Updated on March 4, 2022

When setting up security, you configure the following components:

  • Operator IDs — include information that identifies the user. The ID includes the operator ID name, a log-in password, and the access group to which the operator belongs.
  • Access groups — identify users with the same security requirements. Each user must belong to at least one access group, which is referenced in the user’s operator ID.
  • Access roles — define roles as having certain class access rights. A user can have one or more access roles, which are referenced in access groups. All users in the same access group have the same roles.
  • Privileges — defined to allow a user with a particular role to access certain functions in the application. Privileges are associated with access roles and classes, not individual users. Users have the privileges associated with their access role.
  • Access role obj rules — specify relationships between access roles, the classes a role can access (including at what level and/or under what conditions the access is permitted), and the privileges associated with that class and access role.

The following sections describe how you can modify the standard security components or add your own if necessary.

Tip: You must specify roles when creating access groups. Therefore, you should plan and name the access groups you need before creating roles.
Pega Smart Investigate for Payments Implementation Guide

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us