Business Problem:
The current role-based permissions structure (Agent, Manager, Admin) does not provide enough flexibility for organizations with complex operational workflows. Many businesses — especially those with multiple internal departments — require fine-grained control over what each user can view, edit, or do inside the platform.
This leads to risks such as accidental customer replies, unauthorized data edits, or exposing sensitive information to users who should not have access.
Desired Outcome
  • Introduce a granular permission system that allows workspace admins to customize access levels per user or per role. This should include the ability to enable or disable specific actions, modules, or permissions, such as:
  • Access to Dashboard, Contacts, Messages, Snippets, Users & Teams (but not Workflows or advanced settings)
  • Read-only access to conversations
  • Restricting ability to reply to contacts
  • Restricting ability to send files, surveys, or voice notes
  • Allowing comments only for inter-team collaboration
Use Cases
  1. Multi-Team Operational Workflows
Some customers (e.g., online stores) have an operations team that reviews cases internally.
The desired flow:
  • Customer care assigns a contact to the operations team
  • Operations team reviews history
  • Leaves internal comments
  • Contact is returned to the agent
However:
  • The operations team should not reply directly to the customer
  • Replies must be text-only for some agents
  • Operations team should have limited permissions (no surveys, no attachments, no voice notes)
  1. Restricting Access to Sensitive Contact Fields
  • Currently, contact fields marked as hidden are only collapsed behind a dropdown — but are still accessible and editable.
  • Organizations need stronger control over field visibility to protect internal or confidential data.
  • View-only fields: Users (at least agents) should be able to see certain fields but not edit them.
  • Fully hidden fields: Some fields should be completely invisible to certain roles (not displayed anywhere in the interface).
This is important for companies storing sensitive customer data (financial info, internal IDs, CRM-synced fields, etc.), where only a subset of users should have access or edit rights.