Configuring your operators and security model
During the execution of the New Application wizard, the system creates a copy of the access groups that represent the different personas involved in the application. If you created an application of named MyApp, you must have the following access groups in the system:
Access group
| Access group | Type | Description |
| MyApp:CLMFSCIBSysAdmin | Administration | General administrator |
| MyApp:CLMFSCIB_AppSetup | Administration | User with access to App Studio |
| MyApp:CLMFSCIB_SS_User | End user | Sales Support User |
| MyApp:CLMFSCIB_SS_Manager | End user | Sales Support Manager |
| MyApp:CLMFSCIB_RM_User | End user | Relationship Managers User |
| MyApp:CLMFSCIB_RM_Manager | End user | Relationship Managers Manager |
| MyApp:CLMFSCIB_KYC_User | End user | KYC User |
| MyApp:CLMFSCIB_KYC_Manager | End user | KYC Manager |
| MyApp:CLMFSCIB_BO_User | End user | Back Office User |
| MyApp:CLMFSCIB_BO_Manager | End user | Back Office Manager |
| MyApp:CLMFSCIB_ITAdmin | Administration | IT Administrator |
The system configures all these access groups by default to use new roles that inherit from the out of the box ones. It gives you the ability to create your own privileges and security configuration against out-of-the-box resources. In addition to the general configuration applicable to any Pega application (for example, name, email, location settings, and others), there are two pieces of configuration that are essential to get your operators ready:
- Access group
- The operator must be pointing to one of the access groups, see the list of
access group in a table above. Pega supports
the configuration of multiple access groups per operator, but the CLM
portals are not prepared to switch between access groups, then your operator
can access only to the one marked by default.
For example, if we want our operator to act as the manager of a group of Relationship Managers, it should use the access group MyApp:CLMFSCIB_RM_Manager.
- Organizational unit and work group
- Associate your operators with the operating structure, see Configure your operating structure. Assign the operator to
one of the organizational units and make the work group point to one of the
departments created.
For example, if the operator must be responsible for the Relationship Managers at the Frankfurt booking entity, allocate it to the UPFS-GM-EMEA-DE-UPFSFR organizational unit and to the UPFS_GM_EMEA_DE_RelMgmt work group.
Administer your operators, either to create new or to edit existing ones.
In the header of Dev Studio, click .
Previous topic Registering existing journeys and sub-journeys Next topic Implementing case types