Some decisions deserve a person
Manual Review gives authorized community teams a structured place to evaluate applications, ambiguous security signals and requests for sensitive roles. Reviewers see the permitted evidence, the applicable flow and policy, the member's route and the decision options available for that case.
A focused reviewer queue
Cases can be assigned by role, reviewer availability or policy. Deadlines make unattended work visible. Conflict-safe claiming and decision submission prevent two reviewers from silently applying incompatible outcomes.
CASE · Seller role request
Evidence · Rules accepted · Identity result: threshold met
Signal · New Discord account
Actions
Approve · Approve with probation · Request information
Keep restricted · Reject · EscalateReasons are part of the decision
Every decision records reviewer identity, selected outcome, required reason and resulting access change. The case history preserves assignments, requests for information, escalations and policy/flow versions.
Keep the member informed
Every effective decision has an explicit member-notification policy. Approval, approval with probation and requests for more information always notify the member. A denial or continued restriction can notify the member or be submitted as proactively silent, with notification selected by default.
Silent means no proactive Discord DM. It does not hide the member's real status, remove the community's support or appeal route, or omit Activity and Audit records. Internal moderator evidence stays separate from the safe reason shown to the member.
Discord users can disable DMs. GuildWard records whether delivery was sent, unavailable or failed without reversing the access decision, and keeps a safe outcome available through the member journey.
One or several reviewers
Use one-person approval for routine community access. Pro supports sequential and N-of-M policies when a sensitive role needs separation of duties. The flow continues only when the configured approval rule is satisfied.
Pro Rejoin Guard
Pro can carry an explicit adverse or unresolved access decision across leave and rejoin events. Rejoin Guard is scoped to one Discord server and does not create a shared or global blacklist.
The recommended mode keeps the returning member Restricted and reopens Manual Review. Authorized teams can instead observe the rejoin or deny a new journey. Kick-on-rejoin requires a separate elevated confirmation, and automatic ban is never the default.
Every entry has a reason category, expiry, source decision, audit history and support or appeal route. Leaving and rejoining does not erase an active entry, but it also does not extend one automatically.
Member support and appeals
Communities define the support route and what reconsideration is available. Review screens show only evidence permitted for the decision, while administrators control reviewer scope and retention.
Manual Review supports accountable decisions. It is not proof that a person, identity or community is inherently trustworthy.
Human decisions can still be mistaken, biased or unlawful. Communities remain responsible for fair rules, appropriate training, lawful criteria and a meaningful support route.