Create the Advisors User Account
You must create an account in the Configuration Server that can be used by the Advisors products to connect to and retrieve information from the Configuration Server. In this Deployment Guide, the account is referred to as the Advisors User account, but you can give the account a name of your choice. That is, it is not necessary to name the account Advisors User. The permissions shown in the following Table are required for this account.
The arrow icon in the following roadmap indicates where you are in the Advisors deployment process.
- [+] Install the databases that correspond to the Advisors products you will deploy.
- Create the Advisors User account in Genesys Configuration Server.
- [+] Install the Platform service on servers where it is required for Advisors components.
- Install each adapter that you will use and configure the adapter Application objects with Stat Server connections.
- [+] Install the Advisors components for your enterprise.
- Make any required configuration changes.
Starting with Advisors release 9.0, the Base Object Configuration page no longer exists in the Advisors administration module. Therefore, the following table of Advisors User account permissions has been updated; you no longer require additional permissions related to configuration on the Base Object Configuration page.
|Applications folder||Execute, Change|| Only for Configuration Server 8.1.2 and later. Required for the Platform and AGA user account to connect to the Configuration Server and Stat Servers.|
Change permission is required so the installers can update properties of Application objects that correspond to Advisors servers.
|Hosts folder||Read||Read permission is required on the Hosts folder so that the hosts on which Solution Control Server is deployed can be read from the Configuration Server.|
|Adapter Application object(s)||Read, Change||Starting with release 8.5.2, permissions on the adapter Application object are required for adapter–Stat Server communication. These permissions also allow the migration wizard to update properties in both the adapter Application object and the Stat Server Application object. See Manage Stat Server Instances for more information about the Advisors Stat Server configuration.|
|Stat Server Application object(s)||Read, Change||The Change permission is required starting in release 8.5.2. The migration wizard connects to the Configuration Server in order to update the properties in both the adapter Application object and the Stat Server Application object. See Manage Stat Server Instances for more information about the Advisors Stat Server configuration.|
|*Agent Groups||Read|| Required for CCAdv and WA|
Choose only the sets of objects that you might want to monitor in CCAdv or WA.
|*DNs (of type ACD Queues and Virtual Queues)||Read||Required for CCAdv and WA|
|*DN groups||Read||Required for CCAdv and WA|
|Persons||Read, Read Permissions|
|Change||Required only in the following circumstances:
|Skills||Read||Read permission is required to view skills in the Resource Management Console.|
|*Objects in the Scripts folder (of type Interaction Queue)||Read||Required for CCAdv|
|Access Groups||Read, Read Permissions|
|*Campaigns||Read||Required for CCAdv|
|*Calling lists||Read||Required for CCAdv|
|Roles||Read, Read Permissions||Used to determine functional permissions for users.|
|Business Attributes||Read, Read Permissions||Used to determine access to Advisors metadata objects.|
|Advisors Metrics Business Attributes||Read, Create, Change, Delete, Read Permissions, Change Permissions||Used for the Metric Manager.|
|Folders in Persons||Read, Read Permissions||Required for FA. Read Permissions is necessary to control end users' permissions to see the agent hierarchy.|
|Folder in Agent Groups||Read, Read Permissions||Required for FA. The folder content should represent the FA hierarchy. Read Permissions is necessary to control the end users' agent hierarchy.|
|SDS Application||Read, Change, Read Permissions||Only required if you deploy Supervisor Desktop Service.|
| *You may exclude the following Advisors-supported object types from Read access as a whole, or exclude individual objects within any object type, if any of these objects do not need to be monitored in Advisors:
In the Configuration Server, under Agent Groups, if the folder that you choose for FA does not need to be monitored in CCAdv/WA, then create a separate Advisors account for FA and enter that account when you install the FA component.