Skip to main content

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

Defining an authentication scheme

Updated on April 20, 2021

Pega supports the use of a centralized, automated means of maintaining operator data instead of maintaining it in the Product Designer for Financial Services application.

Product Designer for Financial Services

Use the Security model portion of the implementation planning workbook for the Pega application being implemented to record your decisions during this procedure.

  1. Discuss Authentication schemes with your site’s security and application server teams.
  2. Determine the appropriate authentication model for the organization by defining the access group, portal, and roles for each user type.

For more information on authentication scheme planning, see Authentication in Pega Platform. Configuring the authorization scheme in the application.

Product Designer for Financial Services includes the following pre-defined operators and access groups. You can log in to the application using one of these Operator IDs using the password that you specified when you enabled this operator; to enable Pega-provided operators, see Enabling operators

Operator IDAccess GroupRole










Use these access groups, roles, and privileges for your site needs to control access to the functionalities in the application implementation. To configure an authorization scheme in the application, do the following:

  1. Review the Product Designer for Financial Services access groups and roles:
    • To view access groups: Click Dev Studio > Org & Security > Groups & Roles > Access Groups. The access groups use the preface PegaPDFS.
    • To view roles: Click Dev Studio > Org & Security > Groups & Roles > Roles. The roles use the preface PegaPDFS.
  2. Define access groups for the application. The following access groups are pre-defined in the application:
    • PegaPDFS:Administrator
    • PegaPDFS:Designer
    • PegaPDFS:Manager
    • PegaPDFS:Marketer
    • PegaPDFS:PowerUser
  3. Record the authentication scheme in the Security model worksheet in yourproject’s Implementation Planning Workbook
  4. Identify additional access groups needed for your application.
  5. Identify portals associated with these access groups.
    • Define the access roles and privileges for the application.

Pega authentication schemes work by associating one or more roles to an access group. Roles are additive. The more roles that you add to an access group, the more authorization there is Privileges can be associated with one or more roles. The application comes with the following pre- defined roles:

  • PegaPDFS:Administrator
  • PegaPDFS:ProductDesigner
  • PegaPDFS:ProductManager
  • PegaPDFS:ProductMarketer

For more information, see Access group and role configuration in the Pega 8.4 help.

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