Docs / People
Applicants & bans
How people apply to join through Discord, and how officers approve, reject, or ban.
Signing in with Discord doesn't automatically make someone a member. If they aren't already in your Discord server, they land as a pending applicant — authenticated, but limited to editing only their own profile until an officer approves them.
The join flow
Someone signs in with Discord. If they're already a member of your guild, they're auto-approved and become a member immediately.
If they aren't in your guild yet, they become a pending applicant — visible to officers under Admin → People → Applicants & Bans.
An officer with the members.approve permission approves or rejects. Approving admits them as a full member.
If they later join your actual Discord server and log back in, they're auto-approved on that next login too.
Real bans, not just removals
Banning (members.ban) keeps them out even if the underlying account record is later deleted — the ban is keyed on their Discord ID directly, checked first on every login, and it kills their active sessions immediately. Unbanning clears it. This closes a gap the simpler "just delete the member" approach has: a deleted record used to leave no trace that someone had been banned.
Preview mode (optional)
An install can optionally let pending applicants browse a read-only preview of members-only content, so a prospective member (or a buyer kicking the tires) can see what they'd be joining before you approve them. It's off by default, and even when on it never exposes Settings or lets a pending applicant write anything.