Support permissions & roles
Helpin secures access to customer conversations, inbound routing, and operational configurations through a role-based permission structure. Understanding how permissions and roles interact allows support leaders to grant front-line agents appropriate autonomy while protecting critical routing rules, mailbox configurations, and integrations.
This guide outlines the four core support permissions, workspace role inheritance, precise functional access boundaries, and recommended provisioning structures.
Core support permissions
Helpin defines four distinct permissions governing support operations:
Permission | Description | Functional Scope |
|---|---|---|
| View access to conversations and telemetry | Access inboxes, open and read conversations, view timeline history, inspect customer context sidebars, use canned responses in the composer, and review read-only support analytics. |
| Standard operational actions on conversations | Compose and send customer replies, add internal notes, change conversation status (open, snooze, resolve), set priority, assign teammates or inboxes, apply macros, and create personal or team inbox views. |
| Workspace-wide support administrative control | Configure inboxes, routing rules, mailbox connections, sender addresses, SLA policies, request types and custom fields, customer portal settings, webhooks, live translate, AI settings, and manage shared canned response libraries. |
| Conversation consolidation | Combine two or more related conversations into a single primary record, or separate previously merged conversations. |
Workspace roles and permission inheritance
Helpin structures user access through an additive role hierarchy combined with module-level access:
Roles are additive: **Viewer → Member → Admin → Owner**, with each level inheriting everything below it.
A user receives support permissions based on their assigned workspace role alongside their explicit assignment to the Support module:
Viewer: When granted support module access, Viewers receive
support.read. They can monitor queues and read message threads, but cannot reply, reassign, or alter conversation metadata.Member: Standard team members assigned to Support receive
support.readandsupport.edit. They perform daily customer handling, reply drafting, and queue organization.Admin: Workspace Admins assigned to Support receive
support.read,support.edit, andsupport.admin. They have full access to configuration panels, routing engines, integrations, and automation rules.Owner: Workspace Owners inherit all permissions unconditionally, including
support.adminandsupport.merge.
support.merge is an explicit capability typically granted alongside support.edit to team leads, senior escalation specialists, or support admins to prevent accidental loss of message threads or mismanaged customer timelines.
Access boundaries and restrictions
Helpin enforces role boundaries across settings screens and operational tools:
Settings screens
Settings pages that require support.admin are visibly restricted. Users lacking administrative rights either see these screens in read-only mode or have the navigation items hidden entirely:
Channels & Inboxes: Configuring inbound email mailboxes, chat routing, phone channels, sender display names, and routing scopes requires
support.admin. Users withsupport.readcan view inbox queues and routing setups but cannot alter endpoints.Routing & Triage rules: Creating and modifying automated triage rules, round-robin assignments, and inbox conditions requires
support.admin.SLA policies & tiers: Establishing breach schedules, business hours, and operational tiers requires
support.admin.Request types & fields: Adding or removing ticket types and mandatory conversation fields requires
support.admin.Customer portal: Modifying public portal registration, domain auto-join, and intake policies requires
support.admin.Live Translate & AI settings: Enabling translation engines and automated response workflows requires
support.admin.Webhooks & API integrations: Registering webhook listeners and inspecting signing secrets requires
support.admin.
Composer and canned responses
A distinct permission split applies to canned responses:
Inserting a canned response: Requires only
support.read(andsupport.editto dispatch the final message). Any agent working in the composer can browse, search, and insert existing canned responses.Managing the canned response library: Creating, editing, or deleting canned responses from the workspace repository requires
support.admin. This protects standardized messaging and compliance guidelines from unapproved modifications.
Inbox views
Creating and customizing inbox views does not require administrative privileges:
Any teammate with
support.editcan create, modify, and save custom inbox views and filters.Saved views can be scoped for personal use or shared across team inboxes without altering underlying workspace routing logic.
Merging and unmerging conversations
Merging customer records carries permanent operational consequences:
Merging conversations combines message histories and reassigns timeline events.
Because an incorrect merge can confuse ongoing communications or expose disparate customer interactions, the action strictly requires
support.mergein addition tosupport.edit.Users possessing only
support.editcannot execute merge actions.
Recommended permission configurations
To ensure operational stability, apply the principle of least privilege when configuring user roles:
Role Profile | Assigned Permissions | Typical Assignment |
|---|---|---|
Front-line Agent |
| Day-to-day customer support agents handling incoming chat and email inquiries, updating statuses, and using existing canned responses. |
Senior Agent / Team Lead |
| Senior specialists who handle escalations, clean up duplicate incoming threads, and organize queue backlogs. |
Support Administrator |
| Support leads, technical operations managers, and workspace administrators who manage routing rules, SLA targets, portal configurations, and team permissions. |
Keep the number of users with support.admin small. Restricting administrative rights prevents accidental disruptions to automated routing rules, channel configurations, and webhook deliveries while ensuring front-line agents retain all necessary tools to resolve customer conversations promptly.
Related pages
Was this article helpful?