Stavent roles
Stavent assigns product roles to users based on Discord roles and (optionally) SSO groups. A typical setup includes:
| Stavent role | Typical Discord role | Capabilities |
|---|---|---|
| Owner | Admin | Billing, security settings, integrations, full access. |
| Admin | Lead / Senior Mod | Config, automations, exports, team management. |
| Agent | Support | View/assign tickets, respond, resolve, macros. |
| Moderator | Mod | Moderation actions, case notes, audit logs. |
| Viewer | Staff | Read-only dashboards and reports. |
Discord permission model
Discord permissions come from role hierarchy and per-channel overrides. Stavent recommends:
- Keep ticket channels private by default.
- Grant access via a small number of staff roles (agents/moderators).
- Let Stavent manage per-ticket overrides automatically.
Note
If someone can view the parent category, they may infer ticket existence (even if they can’t read messages). Use a hidden category for strict environments.
Recommended role mapping
- Create Discord roles:
@Support,@Moderation,@Ops. - In Stavent, map them to
Agent,Moderator, andAdmin. - Create an
@On-callrole for escalations.
Common pitfalls
- The bot role is below an agent role, preventing permission updates on ticket channels.
- Ticket categories inherit visibility from a broad “Staff” role that includes non-agents.
- A channel override denies
View Channeleven though a role should allow it.
Tip
When debugging, temporarily create a dedicated
@Stavent Debug role and grant it only the permissions you need. This makes override logic easier to reason about.