Skip to main content


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

Adding the Pega Call security privilege to custom access roles

Updated on October 1, 2021

In Pega Call™ releases 7.4 through 8.6, security enhancements on several rules require that an operator have new privileges to access the rules. Without the new privileges, an operator cannot access the rules required to run the application. An operator must have the crmCanCTIUserRunActivity privilege to access rules that require this privilege.

The following out-of-the-box access roles have been enhanced with the new privilege so that the appropriate operators can access the rules:

  • PegaCTI:CSR
Note: If you are upgrading from an earlier release, and your application uses the out-of-the-box version of these access roles, then your operators will have the required privilege after you update to a higher version of the application.

After you update to a higher version of the application, complete the following steps to check if you need to add the new privilege to any of your access roles.

  1. Review your access groups to determine whether you use any of the access roles that have been updated to include the new privilege.
  2. If an access group does not include an access role with the required privileges, ensure that your operators can access the rules that are required to run your application:
    • If you use out-of-the-box access roles, add the access role to the access group.

      For information, see Adding a role to an access group.

    • If you are using custom access roles, add the privilege "crmCanCTIUserRunActivity" @baseclass to the appropriate custom roles, which internally creates access request object for that respective access role.

      For information, see Granting privileges to an access role.

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