Agent Permissions
Permission for users to log into Softdial Scripter™ are governed according to the following:
Level 1 - basic rules
For a user to log in to
- the Administrator campaign:
- the user must have at least Supervisor permissions. This is a 'hard-coded' rule
- any other campaign:
- the campaign must be running
- the Scripter Engine Config.xml must contain an entry for that campaign naming a valid script. See Configuration
Level 2 - config file
As well as the Level 1 basic rules, Scripter allows further specification via a config file, Permissions.xml.
This file must be placed in:
C:\Softdial\Scripter2\Engine\<tenant>\Scripts (where C is the installation root drive.)
and may be created in several ways:
- Use the example _Permissions.xml (in the same directory) as a template, by simply removing the underscore from the filename.
- Take a copy from the Scripts template folder <install-dir>\Scripter2\Engine\Scripts.
Configuring Permissions.xml
For a specific agent ID, you can configure to either allow, or deny a set of campaign names. See the example Permissions.xml below
Show example Permissions.xml
<?xml version="1.0" encoding="utf-8" ?>
<permissions version="1.0">
<agents>
<!-- This example demonstrates the agent can only access the campaigns 'Mobile' or 'Sales' -->
<agent id="Kate" mode="allow" >
<campaign>Mobiles</campaign>
<campaign>Sales</campaign>
</agent>
<!-- This example demonstrates the agent can access all campaigns except for the campaign 'Mobiles' -->
<agent id="William" mode="deny">
<campaign>Mobiles</campaign>
</agent>
</agents>
<!-- The defaultAgent entry is used when there is no match to an agent.id entry in the agents element -->
<defaultAgent id=" mode="deny">
<campaign>Administrator</campaign>
</defaultAgent>
</permissions>
Take care in selecting whether to deny or allow, as each has implications for any newly created campaigns:
- deny <only these campaigns> - any new campaigns will be automatically accessible
- allow <only these campaigns> - any new campaigns will be automatically inaccessible
If there is no match for a particular agent ID, the defaultAgent rule will either allow or deny in the same way.
Again, to minimise configuration effort, consider carefully if, by default, you want to allow or deny agents to access created campaigns. This will define the default agent rule.
Relying on the defaultAgent is most efficient if the majority of the agents fit in to a single group leaving only a few to be specifically configured .
In the situation where agents are divided in to many groups, where each group must only have access to a specific set of campaigns, then an entry must be created and maintained for each agent.
To bring the file into effect, the Scripter Engine <tenant> service must be started/ restarted.