Earlier each agent had to be given access to explore and recently this feature has been moved over to role to make it easier to grant bulk access to agents.
I understand why this change was done, but tying explore access to a role has an issue. In our case (am an enterprise customer), not everyone in the role is allowed to view Explore.
Since a user can have only 1 role, it's hard and tedious to create 2 versions of each of the roles, one with Explore access and one without.
A better solution would have been based on Group, since a user can be assigned multiple groups. We could create a group that gives access to Explore, and assign it to users who need access.
Please assess if it makes sense to do it this way instead.
Iniciar sesión para dejar un comentario.