You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When searching, agents can still find contacts and conversations, even if this access to contacts and conversations is removed through custom roles.
To Reproduce
Create a custom role removing access to contacts or some conversations;
Assign this custom role to an agent
Access the dashboard as that agent
Use the search bar and search for a contact name or term
Contacts and conversations that contain those names or terms will be available for the agent to access
Expected behavior
Agents should not be able to view these conversations and contacts even if they find them through the search bar.
If access to contacts or conversations is blocked for an agent, that contact or conversation should not appear in the search bar; or, even if it appears, he should not be able to open the contact/conversation details, the contact number should be hidden and the messages too.
Environment
Docker
Cloud Provider
None
Platform
None
Operating system
No response
Browser and version
No response
Docker (if applicable)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
When searching, agents can still find contacts and conversations, even if this access to contacts and conversations is removed through custom roles.
To Reproduce
Expected behavior
Agents should not be able to view these conversations and contacts even if they find them through the search bar.
If access to contacts or conversations is blocked for an agent, that contact or conversation should not appear in the search bar; or, even if it appears, he should not be able to open the contact/conversation details, the contact number should be hidden and the messages too.
Environment
Docker
Cloud Provider
None
Platform
None
Operating system
No response
Browser and version
No response
Docker (if applicable)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: