I wanted to bring up a concern regarding the Supervisor role permissions.
Currently, the Supervisor role allows them to manage agent activation, but we want to ensure that they do not have the ability to manage the queue under user management, such as adding or removing agents, or to view the queue.
Interestingly, we discovered that when Supervisors attempt to add or remove agents, they are able to do so despite an error popup indicating "You do not have the required permissions to perform the requested action." This is concerning and needs to be addressed.
Additionally, we found that if we remove the "queue > view" permission, it removes the queue tab from user management but also removes the Queue Activity from Analytics. This is not ideal, as we need to maintain visibility in Queue Activity while restricting access to manage the queue itself.
Could we define a role permission that separates these cases? Specifically, we need one permission for activation under Queue Activity and another to manage the queue itself without the overlap. This will ensure that Supervisors can perform their duties effectively while maintaining the necessary restrictions.
please vote Separate Queue Management and Queue Activity Permissions
------------------------------
Ibrahim Al Kibssi
Telecom - Infrastructure Engineer
------------------------------