Decide Who Gets Access with Role-Based Access
What’s New! Role Based Access is now more granular. Instead of only turning entire modules on or off, QuickReply now supports Parent–Child RBAC, where a Parent is a main module (like Conversations, Journeys, Campaigns) and Child permissions control specific tabs/views/data export inside that module. How It Works Owner-only configuration: Only the Owner can see and manage Role Based Access settings. Permission matrix UI: The Owner gets a simple checkbox matrix with Admin and Member columns, plus expandable child permissions under each parent module. Parent–Child behavior: Turning on a Parent makes its Child permissions available. If a Child permission is selected and saved, its Parent is automatically enabled. Default access: My Chats stays enabled for both Admin and Member and cannot be turned off. Custom Views supported: The same access logic also applies to Custom Views. Save flow: Changes apply when the Owner clicks Save Changes. Why It Matters Improved control and privacy: Teams can restrict access to sensitive areas while still allowing people to do their core work. Cleaner team operations: New members get exactly the access they need, reducing mistakes and internal back-and-forth. Better scalability: As teams grow, access control remains structured and manageable without manual policing. Things to Know Before Using It If Starred/Priority view is turned off, it will not appear in the UI (even if starring behavior elsewhere remains unchanged). Child permissions depend on their parent module. Selecting a child will automatically turn on the parent. Since only the Owner can edit these settings, decide upfront who should own permission management in the account. To know more check out our documentation
How do you feel about this update?
