Security Policies

A Security Policy allows a user to create custom security roles for each tenant and map them to Genesys Configuration Server Access Groups. During authentication, a user is granted all of the permissions that are combined from roles that are mapped to the Genesys Configuration Server Access Groups of which the user is a member. A role can contain any combination of permissions from three groups: administrative permissions (technical configuration), configuration permissions (business-user configuration), and task-management permissions (the Global Task List view in iWD Manager). For them to function properly, most permissions must be added in groups; for example, modify or delete permissions are useless without the view permission.

Key features of Security Policies include the following:

The following properties and actions are available for Security Policies:

Name

Role name. This is a mandatory field and must be unique within the tenant.

Group Mapping

Configuration Server Access Group mapping. This is a mandatory field.

Description

A plain-text description of the role (up to 4,000 characters).

Is Public

If the role is marked Public, it can be assigned to child tenants.

 

 Available permissions can vary, depending on available modules/configuration.

Note: In the initial 8.0 release of iWD, iWD maintains its own security roles. These roles are independent from Roles that are defined in Genesys Administrator. That is, for a single user that is defined in the Genesys System, the user may be assigned one or more roles in Genesys Administrator, as well as inherit one or more roles that have been defined in iWD Manager. The roles in Genesys Administrator are used to define which tasks a user can perform in specific applications, such as Genesys Administrator itself, as well as Genesys Interaction Workspace. The roles in iWD are used to define what tasks a user can perform in iWD Manager.