Defining a Scope for a Role

A scope defines for which entity a role is relevant. For example, the user can view alarms of the bot called "MyBot".

➢ To define a scope:
1. Before defining the scope, select roles for the policy, as described here.
2. In the Policies page under the Visual Editor tab (selected by default), do the following:
a. In the Scope field, define the Scope for the selected Roles. The following table describes the syntax you can use for defining the scope:

Scope Syntax

Scope is for

*

(Default) All entities (i.e., all bots).

<bot name>
- or -
name=<bot name>

A specific bot (e.g., name=MyBot).

Note: The name is case-sensitive.

pvd=<provider name>

A specific provider (e.g., pvd=MyProvider).

Note: The name is case-sensitive.

tag=<Authorization Tag>

All entities that are configured in VoiceAI Connect with a specific 'Authorization Tag' (authorizationTag parameter), for example, tag=Comp1234.

Using tags is useful as it allows you to assign a role to multiple entities. For example, you may want to assign a role to three different bots. In this case, you would configure the bots with the same 'Authorization Tag' in VoiceAI Connect (e.g., "Comp1234"), and then use its value as the scope ("tag=Comp1234").

Note:

■ This scope is applicable only to these roles: bots, providers, dialout, transcript, and sipladder.
■ The value is case-sensitive.

You can define a scope with multiple values and combined with different scope types, where each is separated by a comma. For example: bot1,bot2,tag=sue,pvd=wow

b. Under the Action group, click Allow or Deny to allow or deny this role-scope entry, respectively.
3. Click Save & Apply Policy.
4. Repeat the previous steps to add additional role-scope entries.