1. Description

By default, there is one role - — sysadmin, which has all rights and access.

The user has the right User is authorised to access this or that page when configured with the necessary permissions.

The procedure for passing the access checks:

Availability of a license;
Permission to access the application;
Permission to access the partition section (for applications that have partitionssections);
Permission for actions in the application/partitionsection.

1.1. Availability of a license

Please get in touch with your Webitel representative to obtain a license.

1.2. App permission

The permission to access the application is defined on the Applications access tab of the role entry, which is on the Roles page from the Permissions category. How to set this resolution can be found here.

Anchor

	1.3
	1.3

1.3. Permission to access the

partition

section

Permission to access a partition section is defined in a modal window (opened through the editing tool of the application containing this partitionsection) on the Applications access tab for the role entry, which is on the Roles page from the Permissions category. How to set this resolution can be found here.

In cases where additional settings are enabled (switch(s) in the on position) on the Objects page (from the Permissions category), access can be granted through the Managed by operations tab or the Permissions tab of the particular entry to which you want to get permission.

Available only for entry from those partitions sections to which access is granted!

Anchor
1.4
1.4
1.4. Permission to action in an application/

partition

section

By default (, all switches on the Objects page from the Permissions category, the switches page are in the off position.

When the Managed by operations and Managed by recordsswitches for the relevant section are in the off position), those users who have , Users with permission to access the application or partition section (see sections 1.2 and 1.3) are allowed all actions.Permission for actions in the partition can be configured:the following actions: read, edit, create, and delete.

Otherwise, action permissions for the section can be configured on the following pages:

1.4.1. Managed by operations

On the Managed by operations tab

of the entry of the particular partition, which is on the Objects page. They are used when additional settings are enabled (on the Objects page, in the entry of the particular partition,
, Users and Roles are selected. Permissions for actions such as Add, Select, Update, and Delete are configured for each of them. These settings apply when the Managed by operations switch
is in
for the
on position
relevant section on the Objects page is enabled (Fig.
7);
5).
1.4.2. Managed by records
On the Managed by records tab of
the entry of the particular partition, which is on the Objects page. You can set default values for new entries in the selected partition (these settings will be set in
a section, default values can be configured. These values will be passed to the Permissions tab when
creating a
new
entry in the chosen partition); AnchorПрава_1.4_SelectПрава_1.4_SelectOn the Role permissions tab to the role entry, which is on the Roles page. Here you can configure rights such as rights to eavesdrop on a conversation, view CDR phone numbers, export data grid, play a call recording
objects are created in the selected section, provided the Managed by records switch for the section on the Objects page is enabled.
Warning
If the Managed by records switch is enabled, the Managed by operations switch will also be enabled!
1.4.3. Role permissions
Role permissions is the tab for roles. Here, additional rights for the role can be configured, such as eavesdropping rights, viewing CDR phone numbers, data export grid, playback record file, and more, as well as global rights
to select, update, delete and create;
on the Permissions tab of the particular entry to which you want to obtain permission. They are used when additional settings are enabled (on the Objects page, in the entry of the particular partition, the Managed by records switch is on (Fig. 5)). Available only for entry from those sections to which access is granted!
Action permissions for a particular created entry can be changed in the tab of the entries, which are located in the following partitionfor viewing, editing, deleting, and creating. More information about these rights can be found here.
Note
Global rights from the Role permissions page take priority over the rights configured on the Managed by operations tab! These rights include Select, Add, Delete, and Update. For instance, if the Role permissions page grants permission to edit, but editing is restricted on the Managed by operations tab, the User with that Role will still be able to edit.
1.4.4. Permissions
Permissions are used when the Managed by records switch is in the on position.
On the Permissions tab, action permissions for specific records are configured.
The Permissions tab is present in objects within the following sections:
Users;
Devices;
Buckets;
Call lists;
Calendars;
Agents;
Teams;
Resources;
Resource groups;
Queues.
In the case when permission to access a partition is available, but additional settings are enabled (switch (s) in the on position) on the Objects page that does not allow viewing, then the right to view the partition may be granted via the Select right If access to the section is granted, but there is no permission for actions on the specific record, the right to perform actions can be provided through the global rights Select, Add, Delete, and Update in the Role permissions tab for the User's Role (see Option 5)4).
Note
The Permissions tab shows only the Roles and Users that you can view. If you do not have permission to view other Users, you will only see yourself and your Roles on the Permissions tab, if they are configured there.
2. Practical examples
A task:
Make settings under which the Test_User user User will have access to view data about the Test_team teamTeam.
Option 1
These conditions are met:
license CALL_CENTER;
the Test_User user User is assigned the Super-admin role Role (Fig. 1). The Super-admin role Role has access to the Admin application (Fig. 2) and the Team partition section of this application (Fig. 3). Configured in the Applications access tab of the Super-admin entry, which is on the Roles page;
Fig. 1. Assigning the Super-admin role
Fig. 2. Allowing the Super-admin role to access the Admin application
Fig. 3. Allowing the Super-admin role to access the Teams partition section of the Admin application
on the Objects page in the cc_team entry, the Managed by operations and Managed by records switches are off. (Fig. 4).
Fig. 4. The Managed by operations and Managed by records switches are off
Option 2
These conditions are met:
license CALL_CENTER;
the Test_User user is assigned the Super-admin role (Fig. 1). The Super-admin role has access to the Admin application (Fig. 2) and the Team partition of this application (Fig. 3). Configured in the Applications access tab of the Super-admin entry, which is on the Roles page;
on the Objects page in the cc_team entry, the Managed by records switch is on (Fig.5).
Image Removed
Fig. 5. The Managed by records switch is on
in the Permissions tab of the Test_team entry, that on the Teams page there is permission to action for the Test_User user, or for the Super-admin role (Fig. 6)
Image Removed
Fig.6. Action permission for Super-admin role
Option 3
With these settings, the user can read, create, edit, and delete on the Teams page.
Option 2
These conditions are met:
license CALL_CENTER;
the Test_User User user is assigned the Super-admin role Role (Fig. 1). The Super-admin role Role has access to the Admin application (Fig. 2) and the Team partition section of this application (Fig. 3). Configured in the Applications access tab of the Super-admin entry, which is on the Roles page;
on the Objects page in the cc_team entry, the Managed by operations switch is on (Fig.75).
Fig. 75. The Managed by operations switch is on
in the Managed by operations tab of the cc_team entry, which is on the Objects page,
there is permission to for the Read action for the Test_User userUser (Fig. 6), or for the Super-admin role (Fig. 8). Role.
Fig. 86. Action permission for Test_User User
With these settings, the user can only view information on the Teams page. Other action permissions can be configured by changing the settings from Forbidden to Allow or Allow with delegation.
Option
4
3
These conditions are met:
license CALL_CENTER;
the Test_User user User is assigned the Super-admin role Role (Fig. 1). The Super-admin role Role has access to the Admin application (Fig. 2) and the Team partition section of this application (Fig. 3). Configured in the Applications access tab of the Super-admin entry, which is on the Roles page;
on the Objects page in the cc_team entry, the Managed by operations and Managed by records switches are on . (Fig. 97);
Fig. 97. The Managed by operations and Managed by records switches are on
in the Managed by operations tab of the cc_team entry, which is on the Objects page, there is permission to action for the Test_User userUser, or for the Super-admin role Role (Fig. 86);
in the Permissions tab of the Test_team entry, that on the Teams page there is permission to action for the Read action for the Test_User userUser, or for the Super-admin role Role (Fig. 6).
Option 5
8).
Image Added
Fig. 8. Action permission for Super-admin role
With these settings, the user can only view information on the Teams page. Other action permissions can be configured by changing the settings from Forbidden to Allow or Allow with delegation.
Option 4
These conditions are met:
license CALL_CENTER;
the Test_User User user is assigned the Super-admin role Role (Fig. 1). The Super-admin role Role has access to the Admin application (Fig. 2) and the Team partition section of this application (Fig. 3). Configured in the Applications access tab of the Super-admin entry, which is on the Roles page;
in the Role permissions tab of the Super-admin entry, on the Roles page, there is the Select permission Select permission (Fig. 109).
Fig. 109. The Select permission
Warning
title Attention!
If none of the above options are met, access is not granted!
With these settings, the user can view information on all permitted pages (see sections 1.2 and 1.3).