Skip to main content

Creating an access group

Suggest edit Updated on November 15, 2021

An access group is a group of application permissions that are used by an operator, external system, or background process. Create an access group to define the actions that are allowed when such an entity uses an application.

Before you begin: To create an access group, you must have the pzCanAlterRoles privilege, which is included in thePegaRULES:SecurityAdministrator role.
  1. In the Dev Studio header, click Create SecurityAccess Group.
  2. Enter a short description for this access group data instance.
  3. In the Access Group Name field, enter a name. As a best practice, use the format of an application name followed by a single colon and a description of the job or user function of the users or other requestors who belong to this access group.
    Do not use an asterisk character(*), parentheses (), or spaces in an access group name. Begin the name with a letter and use only letters, digits, dash, ampersand, period, and colon characters.
    For example: ConsumerLoans:Supervisor
  4. Click Create and open. Result: The access group is created in a ruleset for the application that you are currently logged in to. You can change the ruleset by clicking Edit next to the ruleset name.
  5. In the Application section, in the Name field, press the Down Arrow key and select the name of the application that this access group can access.
  6. In the Application section, in the Version field, press the Down Arrow key and select the version of the application that this access group can access.
    When a user logs in, the ruleset names and ruleset versions identified in the application rule are added to the user's ruleset list.
  7. Grant portal access to the access group.
  8. Add roles to the access group.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

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