Genesys Cloud - Main

Hi

We are busy setting up Role Permissions to View Recordings on PureCloud. We have noted that the Operator Tab in conditions, only has the “Equals” condition. 

Would it be possible to also include a “Not Equals” condition in the Drop-down, as we would like to restrict Users from listening to specific users Recordings?

Further to that, we have also noted that in the Condition Type Drop down, there is no condition type for “Roles”,  could the "Roles" condition type be added in this selection?

We would like to restrict a role, eg. Quality Evaluator, who has access to view all recordings, not to be able to view Recordings for a specific Role, eg. a Management/Exco Role. We have far less users in the Management/Exco Role than all other remaining users and it will make sense if either of these criteria are added.

As it is currently setup, if we need to restrict users from listening to calls for a specific person, we will need to add separate View Recording condition for all users in the system whom the Quality Evaluator role should have access to View, omitting only one or two users that they will not require access to View Recordings for.

Also, every time a new user is added to the system a new Condition will need to be created.

Please advise if either of the above additions can be made to the Operator Tab or Condition Type Tab.

Thanks

Hi Dashendra,

I reached out to one of my coworkers who focuses on Quality Management, and here's his response...

"We can't do that right now. The first feature request seems reasonable (for the permission condition operator of 'not equals'). The second feature request (role as a condition type) could be introduced as another feature request that would serve the problem."

We'll make sure your ideas are entered as enhancement requests on our end.

Thank you!

Clay

Thanks Clay

Hi everyone.

Do you have any news regarding this two features? (“permission condition operator of 'not equals’” and “role as a condition type”)?

I’m asking this because our organization has a similar problem. In our case, we need to have two distinct quality teams that evaluate the same agent group and therefore we have to restrict access between them.

For instance “Quality team 1” has its own “Quality Administrators”, “Quality Evaluators”, corresponding  evaluation processes and results as well as “Quality team 2”, but none of the teams can access to the information (for example, evaluation results) of the opposing team.

I did some tests restraining roles, but without success.

Thank you in advance.

Regards,

Ana Laia