God's Eye setup

Prerequisites

Confirm the intended server and three separate authorities before changing it. The current Discord server owner alone manages owner recovery. A Discord Administrator can use documented server-admin Discord actions but that permission does not grant the protected Council workspace. The workspace requires an active Suite account, a linked Discord identity, the intended server assignment for a Suite Administrator, and the Council capability required by each screen. Also prepare a server evidence channel where the bot can view and send messages.

1. Automatic setup

   In the protected Council workspace, open Setup wizard, choose Automatic setup, then Finish this step to reach Roles. Select separate Verified role, Temporary role, and Quarantine role bindings, or use Create recommended missing roles to create only missing roles with no permissions, mention access, or display color. God's Eye checks Manage Roles and the role hierarchy before saving; Role state updates after a successful save. The wizard reports this step ready only when God's Eye is enabled, its bot is approved, all three role bindings are ready, and logging is configured. If the save is rejected, place the bot role above every selected role and confirm Manage Roles before retrying.

   Expected: God's Eye is enabled, its bot is approved, the three role bindings and logging are ready, and the wizard reports this step ready.

   Related guide

2. Server basics

   From Setup wizard, open Server basics; Finish this step opens Logging. Choose a Default log channel that God's Eye can View Channel and Send Messages in, set deleted-message evidence retention from 1 to 365 days, review Central evidence mirror, and enable or route only the event families the server needs. Open Council access separately to confirm at least one appropriate Council grant; saving logging advances the visible revision, and disabled events stop going to Discord. Check the reloaded default channel, event routes, and revision. If the form is read-only, the linked Suite account lacks Change configuration access and an authorized Council grant must be corrected instead of repeatedly submitting the form.

   Expected: At least one Council grant and the saved default evidence channel are visible for this server.

   Related guide

3. Message protection

   At Message protection, either choose Use recommended protection from the wizard or Choose settings myself. Review Use message protection, Heat recovery, Review point, Quarantine point, and Activity points before saving; this focused save publishes the On or Off choice and one new live rules version while preserving unrelated protection. Check the Current rule state and saved values after reload. If a detailed spam, invite, link, mention, or attachment filter still shows as a draft, open Advanced security rules and activate the reviewed draft before expecting Discord enforcement to change.

   Expected: Message protection reports its current state and a live rules version after a successful save.

   Related guide

4. Staff protection

   Open Staff protection and review Use staff protection, the Short-term monitoring window, the short-term and Hourly limit for each sensitive action, and Trusted staff. Saving publishes one new live rules version; selected trusted staff remain in audit records but are exempt from automatic anti-nuke enforcement. Check the current rule state and reload the chosen limits, then use the Rule simulator for a safe prediction. If the simulator does not reflect a saved change, confirm the page shows a live rules version and that the intended person is not in Trusted staff before changing limits again.

   Expected: Staff protection reports its current state, action limits, and trusted-staff selection.

   Related guide

5. Trusted exceptions

   Open Allowlists and choose the matching scope: Join and staff, Spam, Invite links, Mentions, or Everyone and here. Select only the members, bots, roles, channels, categories, or webhooks that should bypass that protection family; every other check remains active. Saving creates a versioned rules draft rather than changing live enforcement. The "Your changes were saved" message confirms that a draft was stored; it does not read back the draft selections. Current selection exists only on Join and staff, and it shows active rules when active and draft versions coexist. The four scoped allowlist forms also show active values, not the draft. The workspace does not expose a saved draft selection preview. Open Advanced security rules, then use Active and draft versions to identify the new Version with Status Draft. After Council chooses Activate this draft, reload the matching allowlist scope and verify the active selected members, bots, roles, channels, categories, or webhooks. If no new Draft version is listed, keep the change pending instead of activating another version.

   Expected: A new allowlist Version with Status Draft confirms persistence; selected values become active readback only after activation.

   Related guide

6. New members

   Open New member checks, turn on Use new member checks, then review Minimum account age, Require a Discord profile image, Approved bots, Blocked names, and the response for failed accounts and unapproved bots. Council review opens a case without changing roles; Quarantine opens a case and applies the configured quarantine role. Saving publishes one live rules version while preserving raid and staff limits. Check the current rule state and reload the selections. If an intended bot is still treated as unapproved, confirm Allow selected bots is enabled and that the bot appears in Approved bots.

   Expected: New-member checks report their current state and selected review or quarantine responses.

   Related guide

7. Raid protection

   Open Raid protection and choose the Join window, Joins before raid review threshold, and response: Open a Council case or Quarantine the arriving member. Saving applies one new live rules version while preserving account checks. Check the current rule state and whether the page reports an active raid incident. Review lockdown readiness separately before relying on containment or restoration. If lockdown is Blocked until fixed, read its listed prerequisite, role-hierarchy, permission, target, or safe-limit issue and rerun Check readiness before any Apply lockdown action.

   Expected: The saved join window, threshold, response, and separate lockdown readiness are visible.

   Related guide

8. Verification

   Open Verification and review Verification mode (One-click GPS, Instant, or Risk adaptive), Verification target (Everyone or Suspicious joins), Verification enabled, and up to five questions. Saving records these online choices in the protected revision; the inspector shows mode, target, question count, panel status, configured channel, and message binding. Use Post or refresh safely only when the panel channel is already configured. On the member page, God's Eye Internal Profiler is offered only when its card shows Available; a download does not verify a member automatically, and Online verification remains available when the card shows Unavailable. If the panel channel or message binding is unavailable, correct the configured channel and its bot access before reposting.

   Expected: Online verification settings and panel state are visible, while profiler availability stays conditional.

   Related guide

9. Owner recovery

   Open Owner recovery as the current Discord server owner, review Status, Version, Created, and Last used, then choose Create rescue key. Save the displayed value immediately: the rescue key is single-use, revocable, and cannot be read back from the status page. Emergency redemption occurs through the private Discord setup recovery flow, and a used or revoked key is rejected. If Create rescue key is not shown, confirm the linked Discord identity is the server's current owner rather than assuming Discord Administrator or Suite access is sufficient.

   Expected: The current Discord server owner sees an active rescue-key status after saving the one-time value safely.

   Related guide

10. Finish

    Return to Setup wizard and open Finish, then compare the ten-step readiness rail with System health and Delivery health. The wizard is ready only when required bot approval, verification, roles, logging, protection, recovery, map, lockdown recovery, and delivery conditions are all present; Delivery health shows queued, retrying, failed, and recovered Discord work. Reopen any remaining action item instead of treating the guide as complete. If Delivery health says it is not available or shows failed deliveries, keep the affected workflow pending and follow the displayed retry or recovery state before testing another member.

    Expected: The wizard and Delivery health expose what is ready, pending, retrying, or unavailable.

    Related guide

Discord authorization and server selection

Authorize only the official God's Eye bot for the intended Discord server, then confirm it appears in that server before opening setup. Keep its bot role above the Verified, Temporary, and Quarantine roles it must manage, and grant only the permissions required by the selected features. A missing bot, missing Manage Roles, or an unsafe role hierarchy blocks role delivery even when the Suite account can open the workspace.

Protected Council configuration

Suite Owner and Executive accounts have Suite-wide access; a Suite Administrator has access only to explicitly assigned servers. Inside God's Eye, Council owner, Administrator, Moderator, read-only observer, and individual capabilities narrow what each person may view or change. Grant the least access needed, review optional expiry, and verify the Active council list before relying on another administrator.

Protection settings and trusted exceptions

Message, staff, new-member, and raid workbenches publish a new live rules version when their focused save succeeds. Detailed filters and allowlists instead create a reviewable draft that does nothing live until Council activates it. Keep trusted exceptions specific to one protection family, review the current or draft version after saving, and use the simulator before widening an exemption.

Verification and recovery safety

Configure the online mode, target, enabled state, optional questions, three distinct roles, and an existing panel channel before posting or refreshing the verification panel. Members start from that panel, bind their current Discord identity, complete the displayed online checks, and receive role state only after the server-side result is delivered. God's Eye Internal Profiler remains conditional on the member page showing Available; downloading it never verifies a member by itself. Keep owner rescue and lockdown restoration ready as separate safeguards.

Expected results

A saved choice must be visible after reload in its Role state, revision, Current rule state, Active council, panel status, recovery status, or Delivery health readback. The wizard marks a step ready only from stored readiness facts, so a successful button press without the expected readback is still an action item.

Confirm behavior

Use the Rule simulator first because it predicts the active rules without changing members, Discord, or saved configuration. Then test one online member verification from the configured panel and confirm the expected role and local evidence result. Change one bounded protection at a time and review Delivery health before expanding the rollout.

Troubleshooting and next steps

When a screen is unavailable, check the active server, linked Discord identity, Suite server assignment, and Council capability. When saved rules are not active, distinguish a draft from a live version. When Discord did not receive a change, use Delivery health rather than repeating the mutation. Preserve the pending state if the result is uncertain, and never recreate an owner key or recovery action merely to see whether the first one ran.