Skip to main content

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

Understanding project roles and personas

Updated on May 31, 2022

For the best user experience, define how users interact with your application by understanding what roles and personas your project requires. When you know who uses your application, and how, you can update the interactions to provide the most relevant content to users.

To enable customers to start using your application, define operators and access groups. By creating operators and access groups, you specify which elements of your application users can access. As a result, you ensure that every user can access only the features that are relevant to their role. You can increase efficiency exposing users only to data that they need, and improve workload management in your application.

For relevant training materials, see the Organization records and Creating and managing teams of users modules on Pega Academy.

  • Operators

    An operator defines a unique identifier, password, preferences, and personal information for a user. Create operators so that people and processes can access your application.

  • Learning about access groups

    An access group is a group of permissions within an application. Pega Platform uses these permissions for operators, external system access, and background processes. You define an access group for operators who have similar responsibilities. For example, most applications allow case managers to do actions that are different from the actions of regular operators, so case managers and regular operators belong to different access groups.

  • Previous topic Restricting access to operator information in public-facing applications in Pega Platform 8.4 and earlier
  • Next topic Operators

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