Skip to main content


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

Create operators and access groups

Updated on July 27, 2021

The base application provides several standard access groups that can facilitate access to the application.

Pega Client Lifecycle Management for Financial Services Implementation Guide Pega Client Lifecycle Management for Financial Services Implementation Guide Pega Client Lifecycle Management for Financial Services Implementation Guide

Sample operators

If you import the sample data package that comes with Pega Client Lifecycle Management and KYC distribution, some operators are already present in your system.

These default operators do not have access to the implementation layer that you create, but can access the different layers that Pega Client Lifecycle Management and KYC provides out of the box. Use these operators for demo purposes (for example, to run a sample journey before you have your own implementation layer up and running). If you do not import the sample layer, you can create your own operators in the appropriate access group, in accordance with the following table:
Access group/OperatorTypeDescription

CLMFSSysAdmin/CLMFSSysAdmin

AdministratorAdministrator user for the base Pega Client Lifecycle Management and KYC application. Required to access Dev Studio and Admin Studio.

CLMFSCIBSysAdmin/CLMFSCIBSysAdmin

AdministratorAdministrator user for the base Pega Client Lifecycle Management and KYC – Commercial Banking application. Required to access Dev Studio and Admin Studio.

CLMFSRetSysAdmin/CLMFSRetSysAdmin

AdministratorAdministrator user for the base Pega Client Lifecycle Management and KYC – Retail application. Required to access Dev Studio and Admin Studio.

CLMFSUnifiedSysAdmin/CLMFSUnifiedSysAdmin

AdministratorAdministrator user for the base Pega Client Lifecycle Management and KYC – Unified application. Required to access Dev Studio and Admin Studio.

CLMFS_API/CLMFS_API

SystemRequired for the use of the Client Outreach API. The operator that passes with each call to the REST API needs to be part of this access group. See the Client Outreach section in Pega Client Lifecycle Management and KYC Implementation Guide.
CLMFS_WSS/CLMFS_WSSSystemRequired for the use of the Client Outreach WSS demo assets. You must configure the Pega Mashup component embedded in the web self-service application to authenticate users in this access group.
CLMFSRet_WSS_User/[email protected]SystemRequired for the use of the Retail WSS demo assets. You must configure the Pega Mashup component embedded in the web self-service application to authenticate users in this access group.

Application operators

To access the new application that you generate with the wizard, you must create operators. For that purpose, the system generates a group of access groups, all prefixed with the name given to the new application, for example, <app>:CLMFSSysAdmin.

  1. In the header of Dev Studio, click ConfigureOrg & SecurityOrganizationOperators.
  2. In the Operators tab, click the New buttton.
  3. Create an operator in each of the following access groups:

    Application access groups

    Access groupTypeDescription
    <app>:CLMFSSysAdminAdministratorMain administrator of the application. Provides access to Dev Studio and Admin Studio.
    <app>:CLMFS_RM_UserEnd UserAccess group for Relationship Manager Users with access to the Worker portal.
    <app>:CLMFS_RM_ManagerEnd UserAccess group for Relationship Manager Users with access to the Manager portal.
    <app>:CLMFS_SS_UserEnd UserAccess group for Sales Support Users with access to the Worker portal.
    <app>:CLMFS_SS_ManagerEnd UserAccess group for Sales Support Users with access to the Manager portal.
    <app>:CLMFS_BO_UserEnd UserAccess group for Back Office Users with access to the Worker portal.
    <app>:CLMFS_BO_ManagerEnd UserAccess group for Back Office Users with access to the Manager portal.
    <app>:CLMFS_APISystemAccess group to access the application through API (for example, Client Outreach API or Pega API)
  4. Save your changes.
    The operators that you create give access to the main roles and system functions of the application, but are not configured to use any specific operating structure.

    Operators might not have access to all the workgroups and workbaskets required for a fully functional deployment. This access must be granted later, once the operating structure of your organization is configured.

Tags

Pega Client Lifecycle Management for Financial Services 8.7

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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