← Back to Docs

// Guide

Rules Verification

Gate server entry behind an agree-to-rules button that grants a role — optionally requiring a linked RSI account first.

TierFree
You'll needA role to grant and a rules channel.

Rules Verification is the classic "read the rules, click the button, get access" gate. You post a rules embed with an Agree & Verify button; when a member clicks it, StarBot grants them your verified role. Optionally, you can require members to link their RSI account before the button works — a nice on-ramp into Citizen Verification.

Setup

  1. 1

    Create (or pick) the role to grant. Most servers use it to unlock the rest of the channel list — set your channels so @everyone sees only the rules channel and the verified role sees everything else. Make sure StarBot's own role sits above this role in Server Settings → Roles, or it can't assign it.

  2. 2

    Configure the system. In Discord, run /config-rules role [channel] [require_citizen]admin — role is required; channel is where the rules embed will be posted (defaults to the channel you run /post-rules in); require_citizen demands a linked RSI account before verifying. Or do it on the dashboard: Features tab → Rules Verification card → toggle on → Configure.

  3. 3

    Post the rules. Run /post-rulesadmin. A modal asks for the embed Title (defaults to "Server Rules"), the Rules Content, and an optional hex color. On submit, the bot posts the embed with the Agree & Verify button in your configured rules channel.

  4. 4

    Test it. Click the button on an unverified account (or ask a member to) — you should get the role instantly, with a private confirmation.

Here's the dashboard modal:

Guild dashboard — Features tab
FeaturesPermissionsServer StatsAnalyticsEventsTokens
Configure Rules Verification
@Citizen
#rules
Require Citizen link before verifying
CancelSave Changes
Rules Verification card → Configure. The same three settings as /config-rules.

And what members see in the rules channel:

SB
StarBotApp
Server Rules
1. Be excellent to each other. 2. No spam or self-promo. 3. Keep piracy talk in #piracy. 4. Follow Discord's Terms of Service.
✅ Agree & Verify
The rules embed posted by /post-rules — content comes from the modal you fill in.

What happens when a member clicks Agree

  1. Already verified? If the member already has the role, they get a private "you're already verified" note and nothing changes.
  2. Citizen check (if enabled). With Require Citizen link before verifying on, members without a linked RSI account are shown a Link RSI Account button that opens a handle-linking form. Once linked, they click Agree & Verify again.
  3. Role granted. The bot assigns the verified role and confirms privately. No messages are posted publicly, so the rules channel stays clean.
Linked, not verified

The require_citizen gate checks for a linked RSI handle only — it does not require the member to complete full bio-token verification. If you want proof of RSI account ownership, that lives in Citizen Verification; Applications can gate on the fully verified status.

Role hierarchy matters

If members report "Bot lacks permissions to assign this role", StarBot's role is below your verified role in the role list, or it's missing Manage Roles. Drag the bot's role above the verified role and try again.

Command reference

| Command | Who | Purpose | |---|---|---| | /config-rules role: [channel] [require_citizen] | Admin | Set the verified role, rules channel, and citizen-link requirement | | /post-rules | Admin | Compose and post the rules embed with the Agree & Verify button |

Related