Auto-join
Auto-join makes the bot follow members into voice channels without anyone running /discmeet join. You pick which roles act as triggers; whenever a member with one of those roles enters a voice channel, the bot joins and starts recording automatically — joining and recording are a single action.
This is a Pro feature configured from the Settings tab on the dashboard .
When to use it
- Recurring stand-ups where the host always joins first — the bot is just there waiting.
- RPG tables where the DM should never have to remember to start recording.
- Any team where one or two specific people drive when meetings happen.
Admin setup (browser)
- Open the dashboard
- Select your server
- Go to Settings → Auto join
- Turn on Enable auto join & record
- Pick one or more trigger roles (the bot only follows members who hold one of these roles)
- Optional: pick specific voice channels to limit auto-join to. Leave empty to auto-join in any voice channel.
- Optional: under Record as RPG campaigns, map a voice channel to a campaign so auto-joining it records an RPG session instead of a meeting (see Record RPG sessions below)
- Save
When auto-join is on, at least one trigger role must be selected to save. The voice channel list is optional — empty means “any channel”. There is no separate record toggle: whenever the bot auto-joins, it records.
How it works
When a member enters a voice channel, the bot checks:
- Is auto-join enabled for this server?
- Does the member have one of the trigger roles?
- Is the entered channel allowed? (Either the channel scope is empty, or this channel is in the list.)
- Is the bot free to join? (See Multi-channel below.)
If all four are true, the bot joins and starts recording immediately, and posts the same control message you’d see after /discmeet join — Start/Stop buttons and recording status — to your notifications channel (or notes channel as a fallback).
Multi-channel
Auto-join uses the same routing as /discmeet join:
- With multi-channel (Pro+) — assistant bots join in parallel; the main bot doesn’t need to be free.
- Without it — if the main bot is already in another voice channel, auto-join is skipped for the new one. End the existing session first, or upgrade to Pro+ for multi-channel.
Behavior notes
- Already recording in that channel? The bot stays put; the new member is added as a participant via the normal flow.
- Trigger role removed mid-session? Doesn’t end the session; only entry triggers the bot.
- Bots and other automated accounts never trigger auto-join, even if they hold a trigger role.
Record RPG sessions
By default an auto-join records a regular meeting. To record an RPG session instead, map a voice channel to a campaign under Record as RPG campaigns in the Auto join settings. When the bot auto-joins that channel, it records an RPG session for the mapped campaign; any channel without a mapping stays a normal meeting.
The mapping is per voice channel and configured from the dashboard only. Session notes post to the campaign’s channel — split into player and GM notes if the campaign has a GM channel set. You can still start a session manually with /discmeet start and pick the campaign.
Interaction with consent opt-in
Auto-join is independent of Consent opt-in:
- Auto-join decides whether the bot joins and starts recording.
- Consent opt-in decides whose voices are included in the resulting transcript.
If both are enabled, the bot will auto-join and start recording, but only consenting members appear in the transcript.
Related
- Multi-channel overview — run auto-join in multiple voice channels simultaneously
- Basic setup — set the notifications channel auto-join posts into
- Consent opt-in — control whose speech is transcribed
- Who can start meetings — manual
/discmeet startpermissions