Skip to Content
📚 Documentation is in active development — pages marked TODO will fill out over the next few weeks.
Team & permissionsPermission catalog

Permission catalog

A permission is a key (chat.reply, chat.assign, …) that gates a specific action. Each user has a granted set; the default set is determined by role + can be overridden per-user.

Chat permissions

KeyGatesSUPER_ADMINAGENCY_ADMINAGENCY_USERCLIENT_USER
chat.view_inboxSee the inbox
chat.replySend replies
chat.assignClaim / assign conversations
chat.transferTransfer to specific agent
chat.closeClose conversations
chat.view_internal_notesRead internal notes
chat.write_internal_notesWrite internal notes
chat.manage_channelsConnect / disconnect channels
chat.manage_templatesSubmit / edit templates
chat.manage_saved_repliesAdd / edit saved replies
chat.manage_tagsAdd / remove tag definitions
chat.manage_custom_fieldsCreate / edit custom fields
chat.manage_contactsEdit contact attributes / delete
chat.manage_flowsBuild / publish flows
chat.send_broadcastsSchedule broadcasts
chat.manage_dripsBuild drips
chat.manage_automationsBuild automations
chat.manage_keywordsBuild keyword rules
chat.manage_settingsEdit chat policies + business hours
chat.view_reportsView reports panel
chat.export_dataCSV export
chat.manage_groupsCreate / edit groups
chat.make_callsVoice call from inbox

Per-user overrides

/dashboard/team → user row → Edit permissions → toggle individual keys. The override layer is fail-closed: when in doubt the role default wins, BUT an explicit deny override always overrides the role default.

How fast do overrides take effect?

Permission overrides take effect for the affected user within ~5 seconds — the platform caches the merged permission map briefly for performance, then refreshes on the next request.

Last updated on