Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Defining operator contact information and application access

Updated on April 5, 2022

Define an operator's contact information, application access, and localization information so that operators can be communicated with and can access the required applications. The access groups that you specify affect which rulesets, ruleset versions, and portals the operator can access.

Before you begin: Create an operator as described in Creating operator IDs or Adding an operator by using the organizational chart.

For details about the fields on this screen, see Fields for operator contact information and application access.

  1. On the Profile tab, in the Contact Information section, define personal information for the operator. Full name is required.
    • Image
    • Title
    • First name
    • Last name
    • Full name
    • Position / job title
    • Phone
    • Email
  2. On the Profile tab, in the Application Access section, list the access groups that the operator can choose from at run time. Identify the default access group by clicking the radio button next to the access group name.
    • To view the Application Access section, you must have the pxCanManageUsers privilege, which is included in the PegaRULES:SecurityAdministrator role.
    • The application for each access group is displayed. To see the roles in an access group, click the Expand row icon.
  3. On the Profile tab, in the Localization section, list the operator's default locale and time zone.
  4. Click Save.

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