Private delivery by default
GuildWard sends a short-lived continuation by Discord DM first. If direct messages are unavailable, a configured private channel can provide a fallback without exposing the route to other members. Expired or replaced links lead members back to a clear support path.
A scoped browser session
The one-time continuation becomes a narrowly scoped browser session. The member sees the community identity, purpose, required step and support instructions—not an unfamiliar generic gateway.
CAPTCHA is one step, not the whole product
Cloudflare Turnstile can help distinguish legitimate browser interaction from automated abuse. A flow can also include rules, questions, linked accounts, age assurance, identity checks, probation or human approval.
Complete verification does not automatically make a member trusted. GuildWard can continue with probation, additional steps or human approval.
Discord role reconciliation
After a successful route, GuildWard applies the configured role outcome and confirms the resulting Discord state. Retries remain tied to the same journey, and transient Discord errors do not create duplicate access decisions.
Passwords stay with Discord
GuildWard never asks for a Discord password or QR-code login. Administrator authentication uses Discord OAuth, and member verification uses the community's configured steps.
Failure and support
Every flow defines expiry, retry and failure behavior. A member may receive another step, remain restricted, enter Manual Review or contact the community through its support route. GuildWard does not imply Discord endorsement or decide a community's membership rules.