Configuring RMC Users in the Genesys Configuration Layer (8.5.101 Only)
With the appropriate configuration, any Advisors user in release 8.5.101 and later can use the Resource Management Console (RMC). You configure a user’s access to RMC in the Configuration Layer.
When configuring RMC users, consider the following:
- In RMC, users see only agents and agent groups to which they have been granted at least Read permission in the Genesys Configuration Layer.
- You can control what each user can do in RMC. For example, certain users might be able to change agents' skills in RMC, while other users cannot. See Advisors.RMC.ManageAgentSkills.canView and Advisors.RMC.ManageAgentStatus.canView for specific information.
Genesys recommends the following configuration when you assign RMC access permissions to a user:
- Create an access group; for example, RMC Users Access Group.
- Assign the permissions to the access group.
- Add the users as members to the access group.
The following procedure assumes you are using an access group of users who will have access to RMC on the Contact Center Advisor and/or Workforce Advisor dashboard.
See the following Help documents for detailed information about using the Genesys configuration interface available in your enterprise:
Procedure: Assigning User Permissions for RMC Access
To configure User and Access Group objects in your enterprise to allow access to the RMC.
- You have created an access group to contain users who will have access to RMC. (You will add users to this access group as part of the following procedure.)
- You are logged in to the interface you use to configure Genesys applications (Configuration Manager, Genesys Administrator, or Genesys Administrator Extension).
- In the Genesys configuration interface, create a new person in your SDS-monitored tenant for each user who needs access to RMC. This can be the Environment tenant, or another tenant. For each person, do the following:
- If you use SDS release 7.6.300.09 or earlier in your environment, ensure that the Agent check box is selected (that is, identify this user as an agent). Selecting the Agent check box is no longer required starting with SDS release 7.6.300.11.
- In the Annex, create a new section named [security].
- Add the following properties to the section:
- Supervisor = 1
- SupervisorAdhoc = 2
- SupervisorExtended = 10
- SupervisorMonitoring = 1
- Save the person.
- Navigate to the access group that you created to collect the RMC users and make the following updates:
- Add the default user to the list in the Permissions and give that user Full Control as the type of access (if this does not already exist).
- Save the access group.
- Change the permissions of the following objects, as described below, to grant additional permissions to the access group:
- Read on the Environment tenant object. No propagation of this permission to contained objects is required.
- Read and Execute on the application named default in the Environment tenant. Read on any user-created folder that contains the application.
- Read and Execute on the application object for the SDS application, in the Environment tenant. Read on any user-created folder that contains the application.
- In a multi-tenant deployment, Read on the tenant object that contains the RMC user. No propagation of this permission to contained objects is required.
- In the tenant that contains the RMC user, Read on agent groups that the user will work with in RMC. Read on any user-created folder that contains the agent groups.
- In the tenant that contains the RMC user, Read and Change on users (persons) that the user will work with in RMC, although starting with CCAdv/WA release 188.8.131.52, it is sufficient to apply the Read permission only (the Change permission is not required). Read on any user-created folder that contains the users (persons).
- Read on skills that the RMC user will manage for users (persons). Read on any user-created folder that contains the skills.
Restart the SDS server. If there are hundreds of agents, the SDS server can take some time to completely start.
If you use SDS release 7.6.300.09 or earlier, wait until you see the following messages in the SDS server logs before proceeding:
22 09 15:18:34:472 [ Stat Initializer] INFO GSD.Stat Service Stat on request is set to true
22 09 15:18:43:691 [ StatQueue] INFO GSD.Stat DIM Stat initialization complete (Super queue)
22 09 15:18:43:691 [ StatQueue] INFO GSD.Stat DIM Stat initialization complete (Priority queue)
22 09 15:25:54:582 [ StatQueue] INFO GSD.Stat DIM Stat initialization complete
22 09 15:37:53:551 [ http-8080-1] OFF SDS
Supervisor Desktop Service: 7.6.300.09
If you use SDS release 7.6.300.11 or higher, it is not necessary to wait for the Stat initialization complete message in the logs. Instead, watch for the following message in the SDS server logs, which indicates that SDS is ready (that is, all the configuration objects are loaded):
01 04 17:30:36:828 [ Init Ail Logic] OFF SD.Directory Manager Supervisor Desktop Initialized:
Supervisor Desktop Initialized.
- Restart the Geronimo application server in which RMC is running.
When you add users, change users, or remove users in the Configuration Layer, the SDS server should pick up these changes and they should be reflected in the RMC without further action. If such changes are not
visible in the RMC, restart the SDS server after you are done working with the users, and then restart the Advisors Geronimo server on the node that is running the RMC. This will ensure that SDS and Advisors modules use your changes.
- See Next Steps for information about assigning Advisors permissions to the new user.
In addition to the permissions that you assign to the user in the Configuration Layer, the user needs additional permissions assigned as options in the Annex
of a role. Review the following Advisors permissions for additional information:
This page was last modified on October 31, 2017, at 09:18.