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.

Permission access templates in Pega Sales Automation (8.3-8.4)

Updated on September 10, 2021

In Pega Sales Automation™ 8.3, for security reasons, operators are no longer shipped. The default operators, located in the PegaCRM-Data_SFA-OperatorAccess class, are removed from the product. Operators are replaced with the system access templates, which are located in PegaCRM-Data-SFA-OperatorAccess-Template. Access templates provide a convenient way to set permissions on operators that must be saved to the operator record.

Note: In Pega Sales Automation 8.2 and earlier, templates for access permissions for operators were associated with these operators, so when you created new templates for operator access, you also had to create a default operator. You can then use that operator to apply permissions to other operators. In Pega Sales Automation 8.3, access templates are no longer associated with operator records and you can apply them individually.

System-generated access templates

System-generated access templates are included in the product. If a default operator was created before Pega Sales Automation 8.3, it still contains the same permission settings.

System-generated access templates are the final permission settings, which means that you cannot change the names of the templates or deactivate these templates. Also, you cannot add more secondary territory rows to these access templates. After you apply these access templates to operators, you are no longer able to change them on the operator level. For more information, see Applying access templates on operators.

New system-generated access templates are created by Sales Ops when creating a new territory. For any new territory, an access template already exists.

If you upgrade from earlier versions, no additional action is required, because the Validate and Save activities in the PegaCRM-Data-SFA-OperatorAccess and PegaCRM-Data-SFA-OperatorAccess-Template classes automatically move permissions definitions.

User-generated access templates

By default, the user-generated access templates list is empty. User-created access templates are not the final permission settings. After you apply these access templates to operators, as a Sales Ops, you can always change it. Compared to system-generated access templates, there is no limitation in creating these items, except for having multiple access templates with the exact same name.

Viewing access templates

  1. Log in to Pega Sales Automation as a Sales Ops operator.
  2. In the navigation panel, click Tools > Access templates.
    Note: All access templates are PegaCRM-Data-SFA-OperatorAccess-Template class instances.
  3. On the Manage access templates tab, perform either of the following actions:
    • Review system-generated access templates.
    • Review user-created access templates.

      After you create access templates, they display on the user-created access templates tab.

Editing access templates

  1. Log in to Pega Sales Automation as a Sales Ops operator.
  2. In the navigation panel, click Tools > Access templates.
  3. On the Manage access templates tab, select any access template that you want to edit, and then perform any of the following tasks:
    • Deactivate an access template by clearing the Active check box.
    • Add secondary territory rows per level by clicking the plus icon.
    • Change any of the access rights by clearing check boxes that correspond to particular actions, for example, creating organizations.

The territory ID is saved on the access template instance. It is used to filter the list of available access templates based on the territory signature. Local Sales Ops do not see any access templates in the territory hierarchy above their own territory. If there is no territory assigned, the system adds a global territory (BT1). Only Global Sales Ops and system administrators can see all user-created access templates.

  1. Click Submit.

Creating access templates

  1. Log in to Pega Sales Automation as a Sales Ops operator.
  2. In the navigation panel, click Tools > Access templates.
  3. On the Manage access templates tab, click Create access templates.
    1. Enter an access template name.
    2. Define access rights for this template.
    3. Add secondary territory rows per level by clicking the plus icon.
  4. Click Submit.

Applying access templates on operators

  1. Log in to Pega Sales Automation as a Sales Ops operator.
  2. In the navigation panel, click Operators and select an operator that you want to update access permissions to.
  3. Click Actions > Update Access & permissions.
  4. On the Operator access tab, perform any of the following tasks:
    • To use a system-generated access template:
      • Select any operator. The operator also indicates the access group that you need to apply on the operator.
      • Select the Use default operator access? check box.
      • Leave the default primary territory.
    • To use a user-created access template:
      • Select any operator. This is always needed for access group assignments.
      • Clear the Use default operator access? check box.
      • Choose an access template from the drop-down.
      • Select any primary territory.
    • Change any of the access rights by clearing check boxes that correspond to the particular actions, for example, creating organizations.
  5. Click Submit.
  • Previous topic Pega Sales Automation Hybrid Client mobile app deployment (7.4-8.4)
  • Next topic Editing work object templates in App Studio for Pega Sales Automation (7.4-8.4)

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us