Setup

Build and keep the server structure consistent: permissions, bot messages, health checks, and backups. Channel layout lives in a dedicated guide: Discord Schema.

Discord Schema

Visual blueprint of categories and channels that opens from your live Discord layout. Edit, then Sync to create missing channels and remove extras.

Open the full Discord Schema guide →

Permissions

  • Loads live Discord roles and channel overrides into an editable draft with undo/redo.
  • Use the permission matrix (channel or category mode) to grant or deny what staff and members can do.
  • Reload from Discord to refresh; Sync to Discord to push the draft. Save a backup first if you’re rewriting large trees.

Role tags & hierarchy tips

Tags next to roles are status hints, yellow means “fix hierarchy,” not “Permissions is broken.”

  • Bot · locked, Aeon’s own Discord role. Discord never lets a bot edit itself; change name/color in Server Settings → Roles. Sync skips it on purpose.
  • Managed, integration roles (other bots). Sync skips them.
  • Below bot (yellow), that role sits above Aeon in the Discord hierarchy, so Sync can’t edit it yet. Drag Aeon higher under Server Settings → Roles, then Reload from Discord.

When roles are below the bot, a dismissible yellow banner explains the steps. Dismiss hides it for this browser session; the tags remain so you can still see what’s skipped.

Message Builder

  • Compose embeds and bot posts with a live preview.
  • Pick a Discord channel, then Deploy to post or update the message as Aeon.
  • Reuse content via Templates & Backups when you need the same panel on multiple servers.

Server health

  • Rescan Schema and Permissions drafts for role, channel, permission, and security issues.
  • Filter findings by severity (critical / warning / info) and category.
  • Jump to Schema or Permissions from a finding, or apply supported fixes in bulk when the UI offers them.

Templates & Backups

  • Browse My templates, official presets, and an account library. Create templates from current drafts.
  • Share with codes (ETY1.…) to import/export between servers.
  • Store backups of server/draft state before risky syncs so you can roll back.

ETY1 share codes

Move Schema, Permissions, packs, and backups between browsers with one copy-pasteable string, no file upload. Open the ? next to the Templates & Backups title (or How ETY1 works in Aeon library) for the same walkthrough in the dashboard.

Treat codes like private config. An ETY1. code is base64url-encoded JSON, not encryption, anyone with the string can read the full draft.

Kinds of codes

Schema

Categories and channels only.

Permissions

Roles, base perms, and channel overrides.

Pack

Schema + permissions as one unit.

Backup

Timestamped snapshot of either or both drafts.

Create a code

  1. Find the item, open Templates & Backups → My templates or Backups.
  2. Copy the code, use Export / share on the card. The code is built in your browser and copied to the clipboard; nothing is uploaded.
  3. Paste elsewhere, into chat, notes, or another browser’s import / library field.

Import & apply

  • Apply, writes into this server’s drafts for review. You still Sync from Schema / Permissions to change Discord.
  • Add to mine, copies into My templates without changing live drafts.
  • Paste import, use Paste template code on Templates & Backups for a one-off restore.
  • Publish to Account library, Aeon library → Account library → Upload template, paste a code, optionally rename / describe it, then Publish. Entries stay in this browser’s local storage until server sync exists.

Before you share

  • Don’t paste codes in public channels, they include roles, channels, and permission bits.
  • Take a backup before applying someone else’s pack so you can roll back.
  • Don’t hand-edit the base64 section. Whitespace is stripped on paste, but truncated or edited codes fail to decode with a clear error.

Setup wizard

Use this after Schema and Permissions are in place so Safety tools have the roles and channels they need. Open the info control next to the ready chip on Safety → Setup for the same walkthrough in the dashboard. After the wizard, message filters live under Safety → Content & spam.

What this page does

Four steps to get Safety running, permissions, quarantine, content filters, and domains. Work through each node’s checklist, then export your config to reuse on other servers. Click a node on the step bar anytime to review that step.

Steps on the progress bar

Bot permissions

Confirm the bot role can manage roles, channels, and messages so every safety module can enforce. Fix yellow or red checklist items in Discord → Server Settings → Roles, then return here to re-check.

Quarantine

Create or link a stripped quarantine role and an isolation channel. Auto-mod holds, raid mode, and account-age gates all depend on this step being ready. You can create them from the checklist when those pieces are missing.

Content & spam

Turn on spam, word, and invite filters, set punishments, and clear any missing permissions. Incomplete rows jump you to Safety → Content & spam to finish setup.

Domains

Enable anti-link and build allow / block host lists so phishing and unwanted URLs get stripped. Domain lists live on Content & spam → Links. Export later if you want the same lists on another server.

What the step colors mean

The progress bar uses color so you can see where you are and what’s left, orange marks the incomplete step you’re viewing, green means ready, and grey is still ahead.

Orange, viewing (incomplete)

The step you’re looking at isn’t ready yet. Finish its checklist before moving on.

Example: Bot permissions selected while Manage Roles is still failing.

Green, ready

That step’s checklist passed. A green connector only appears between two ready steps.

Example: Quarantine role and channel linked; the node shows a check.

Grey, still ahead

Not selected and not ready yet. Click a node anytime to review that step’s checklist.

Example: Domains greyed out while you’re still on Quarantine.

Export & import

Templates

Use Export template to copy or download safety JSON, then Import template on another server to reuse the same stack. Review Safety (Content & spam, Raids, Anti-nuke) after importing.

Suggested order

  1. Shape channels in Discord Schema.
  2. Map staff roles under Permissions.
  3. Run Server health and clear critical findings.
  4. Save a backup, then deploy welcome or rule messages with Message Builder.
  5. Walk through the Setup wizard before turning on Safety features.
  • Home, setup gaps that point back here.
  • Safety, turn on defenses after structure is stable.
  • Moderation, cases, appeals, and the warn ladder.