General details of how to create or import users into Scripting are covered in the Scripting User Guide.
The directions below describe the specifics for creating any users that will be logged into the Workspace and processing popped Workflows. Any users who will only access Scripting from outside of Workspace (for instance, your Workflow designers or system managers) can be created without the described limitations.
Forms Authentication
If using Forms authentication, users must be created in Scripting with usernames matching their Workspace usernames. Their password must be set to the value specified in the CallScripterPassword option of the Genesys Administrator Configuration article, due to a limitation that prevents Scripting from knowing the user's Workspace password and authenticating against that.
Windows Authentication
If using Windows authentication, users must be created in Scripting that match the the Windows accounts of the desired users. No password need be specified.
Note: unless the Workspace environment is also using Windows authentication, the user accounts may differ between the Workspace environment and Scripting.
Groups
Each user must be a member of a Group that is assigned to both the Campaign and Workflow within Scripting. If the user isn't a member of an appropriate group, then they will be presented with an error message when attempting to pop a Workflow, as shown in the Agent Experience article. As users won't interact with the Scripting Desktop or other areas like that, it may be simplest to assign all users to the System group.
The Groups feature in Scripting is not directly used for the Genesys integration, and will have no bearing on Workspace' user permissions. This activity should be carried out in the Genesys Administrator instead.
