Server Verified Roles
Who your dynamic channels are for. On a server that makes new members verify first, pick the role they earn - @Member, say - and the bot keeps everyone without it out: the generator, its category and every room it makes are gone from their channel list. The same roles are what a room's Private and Hidden act on. Out of the box the list is @everyone, which keeps nobody out. It is free.
@everyone by default
Every member sees the generator and every public room.
Narrowed to a role
Pick the roles your members earn - everyone else sees neither the generator nor its rooms.
What privacy works on
Private stops these roles joining a room, Hidden stops them seeing it.
Per generator
A generator can keep a list of its own instead of the server's.
How It Works
It is built for servers that make new members verify first - read the rules, pass a captcha, get a role - before they can see anything. The rooms follow the same gate:
- Pick the roles your members earn - @Member, say. Left at @everyone, the default, there is no gate: every member is on the list.
- Everybody without one is kept out. The generator, its category, its control panel and every room it makes disappear from their channel list - they can neither open a room nor join one.
- A room's privacy works on the same roles. When its owner sets it Private, the roles on the list can still see it but not join; Hidden takes it off their list.
What it does to permissions
The bot writes this onto every room, and rewrites it whenever the list or the room's privacy changes:
| Who | Public room | Private room | Hidden room |
|---|---|---|---|
| The roles on the list | See and join | See, cannot join | Cannot see it |
| Everyone else | Cannot see it | Cannot see it | Cannot see it |
| Members the owner trusts | See and join | See and join | See and join |
| Members the owner blocks | Cannot see it | Cannot see it | Cannot see it |
| Staff roles | See and join | See and join | See and join |
"Everyone else" only exists once the list is narrower than @everyone: a public room is then public to the roles on the list, and nobody else sees it at all. The generator, its category and its control panel are kept to the same roles. A room's owner always gets into it, and Discord lets members with Administrator into every channel.
Through a member's eyes
Sam's Discord, on a server where newcomers see only #rules and #get-verified until they earn @Member. Press Next to see what the verified roles change for Sam.
Verified roles: @everyone
The default. Every member sees the generator and the public rooms it makes - Sam, who has just joined the server and holds no roles yet, included.
Setup
The verified roles are set once for the server, and every generator follows them unless it has a list of its own.
Step 1: Open the server settings
Run /setup and press ⚙️ Edit Server Options.
Or skip straight to a menu of just the three role settings with /manage roles:
Step 2: Pick Verified Roles
Step 3: Pick the roles
Pick up to three roles. Each pick replaces the whole list, so pick every role you want together:
It is saved the moment you pick, and the bot rewrites every generator that follows the server's list there and then - its category, the generator, its control panel and the rooms already open. Clear hands the channels back to @everyone.
A List per Generator
A generator can keep a list of its own, which replaces the server's for it - one generator kept to @Gamer, say, while the rest follow the server. Run /setup and pick the generator under Edit a master channel - or use /manage edit - then ◎ ∙ Select Edit Option → ∙ Edit Channel's Verified Roles, pick the roles and press ✔ Finish.
Until it has a list of its own, the generator reads (from the server options) and follows the server's. Turning Include everyone role on there puts it back on the server's list. The wizard that makes a new generator asks for its verified roles too, as its third step.
On the Dashboard
On the dashboard, the server's list is under Server Options → Roles → Verified roles. Saving it rewrites the generators that follow it, the same way /setup does.
Permissions
| The bot needs | Why |
|---|---|
| Manage Channels, Manage Roles | To write who may see and join onto the category, the generator, its control panel and the rooms |
| View Channel, Connect | It can only grant a permission it holds itself |
/setup checks for everything the bot needs before it opens, and says what is missing.
Things to Know
- Auto-scaling pools do not use it. An auto-scaling pool's rooms take their permissions from the pool's category, which you set in Discord.
- Three roles at most from Discord's picker, and the picker does not open with the current ones ticked - pick the whole list each time.
Troubleshooting
- Newcomers can see the rooms - the list is still @everyone. Narrow it to the role your members earn.
- Somebody holding the role cannot see the generator - check whether the generator has a list of its own. The
/setupscreen marks a generator that follows the server's with (from the server options). - Somebody without the role got into a room - the owner trusted them, they hold a staff role, or they are an Administrator.
Questions
Do I need to set verified roles?
Most servers do not - keep @everyone. Narrow it if new members cannot see your channels until somebody gives them a role; otherwise a public room shows up for them anyway.
Verified roles or staff roles?
Verified roles are who the rooms are for, and who a private or hidden room shuts out. Staff roles are who it never shuts out.
Does it cost anything?
No - verified roles are free on every server.