Who Can Start Meetings
DiscMeet controls who can start meetings (and join, stop, etc.) based on permissions and roles.
Who has permission
A user can start meetings if any of these is true:
- Server owner — Always has permission
- Manage Channels — Users with this permission can always start meetings
- Meeting access role — Users with one of the roles configured in
/discmeet setup
Meeting access roles
In /discmeet setup, you can select 0–25 roles that are allowed to start meetings. This lets you grant meeting access without giving full Manage Channels.
Examples:
- A “Meeting Host” role for team leads
- A “DM” role for D&D game masters
- A “Transcription” role for designated note-takers
If no roles are set
If you leave the meeting access roles empty, only users with Manage Channels (or the server owner) can start meetings. This is the default restrictive behavior.
Commands affected
The same permission check applies to:
/discmeet join/discmeet start/discmeet stop/discmeet retry/discmeet setup/discmeet campaigns/discmeet characters/discmeet manage/discmeet status
The dashboard has its own access rules for billing and server settings—typically server owner or admin for sensitive screens.
Transcription consent (different from “who can start”)
Consent opt-in is separate from meeting access roles. It controls whose speech is included in the recording and transcript when your admins enable it. Members use /discmeet consent to join or leave the manual list; admins configure roles in the Settings tab on the dashboard .
Error message
If a user without permission tries to start a meeting, they’ll see:
You need Manage Channels permission or be the server owner to start meetings.
To grant access, either give them Manage Channels or add one of their roles to the meeting access roles in /discmeet setup.