Configuration

Everything a server owner sets up, in the order to do it.

All of this lives under Server → Management → Settings and requires you to be the server owner. Nothing here is mandatory except the invite itself — modules are independent, so set up only what you will use.

Getting started

Invite the bot. You need Manage Server in the target Discord. Grant the permissions it asks for — Ban, Kick and Moderate Members back the moderation commands, and Change Nickname is needed for per-server bot naming.
Open the dashboard. Sign in at /dashboard and pick your server.
Choose your modules. Settings → Feature Modules. Staff Hub and Faction Hub are on by default; switch off what you do not need.
Set up Permits. Settings → Permits. This replaces the old single staff role — see below.
Decide on message logging. Settings → Data & Privacy. Off by default; leave it off unless you need it and have told your members.
Optional integrations. Bloxlink for Discord↔Roblox linking, and the in-game scripts for join/chat logging and remote control.

Permits

A permit is a named bundle of permissions granted to one or more Discord roles. A member holds a permission if any of their roles appears in any permit granting it. Permits only ever add access — they can never remove what a server owner or someone with Manage Server already has.

Permissions come in two levels. A category — Moderation, Sessions, Management — is a group of individual actions. On the Permits page, clicking a category card opens it and lets you switch its actions on one at a time; the tick box in the card's corner grants or clears the whole category at once. Grant a role Moderation in full, or just moderation.logs so a trial moderator can read the feeds without being able to wipe them.

Category	Actions
`staff`	Access the Staff Hub, moderator panel, and server overview. `staff.panel` — Open the Staff Hub moderator panel and see the live session. `staff.lookup` — Search server members and look up Roblox or Discord profiles. `staff.shifts` — Clock in, take breaks, and end their own staff shifts. `staff.shiftsManage` — Clock another member in or out, and read anyone's recorded shift time. `staff.records` — Read the promotion, demotion and infraction history of this server's staff. `staff.recordsIssue` — Promote, demote and issue infractions — posts to Discord and can move rank roles. `staff.leave` — File their own Leave of Absence or Reduced Activity request, and see their own leave history. `staff.leaveManage` — Approve or deny leave requests, file one on someone's behalf, and see who is away.
`moderation`	Read and clear the server's log feeds. `moderation.logs` — Read the join, game and moderation log feeds. `moderation.logsClear` — Permanently wipe a log feed for this server. `moderation.cases` — Review and edit moderation cases. (not built yet)
`events`	Trigger in-game events and lockdown protocols. `events.trigger` — Run pre-made in-game events — earthquake, fire, reactor, detonation. `events.protocols` — Declare lockdown radio codes — Amber, Blue, Green, Red, Black. `events.designations` — The Head Event Host's grant: rename the site, the announcer and every event and lockdown code, in game and on the dashboard. `events.design` — Write, rehearse and publish this server's own custom event runbooks — stages, cues and sequences. `events.designAdvanced` — Write raw game commands into a runbook, instead of only the actions the designer offers. Needs Design Events as well.
`sessions`	Control the live session phase. `sessions.status` — Set the session phase — SSU Poll, Preparing, Online, Offline. `sessions.ssu` — Post startup polls and session announcements. (not built yet)
`faction`	Run this server's own faction — roster, recruitment, posts and bot. `faction.manage` — Open the faction dashboard and read its history. Granted by everything below. `faction.identity` — Rename the faction and change its description, icon, invite and links. `faction.roster` — Add and remove members, move them between ranks and divisions, set their status. `faction.applications` — Open and close recruitment, write the questions, and accept or reject applicants. `faction.posts` — Write announcements and events, and push them out through the bot. `faction.bot` — Switch the bot on or off, bind its channels, and change how it looks. `faction.hubs` — Ask a site to take this faction on, leave one, and appeal what they put on its record.
`factionHub`	Manage faction records, rosters, and applications. `factionHub.staff` — Open the Faction Hub staff dashboard and act on any faction. `factionHub.factions` — Add a faction and edit its record. Deleting one is separate. `factionHub.factionsDelete` — Remove a faction and its roster, history and applications for good. `factionHub.warn` — Put a warning on a faction's record. `factionHub.strike` — Put a strike on a faction's record — the heavier of the two. `factionHub.appeals` — Accept or reject an appeal, and lift a punishment already issued. `factionHub.roster` — Edit faction rosters, ranks and membership. `factionHub.applications` — Decide Faction Hub application submissions.
`management`	Server settings, audit logs, and analytics. `management.settings` — Change module toggles, channels and server settings. `management.audit` — Read the record of who changed what on this dashboard. `management.analytics` — View server activity and usage analytics.
`roleplay`	The in-universe terminal: its document database and site clearance. `roleplay.docs` — Write, publish and archive the site's SCiPNET documents. `roleplay.clearance` — Map Discord roles onto in-fiction clearance tiers. `roleplay.manage` — Run roleplay sessions and scenes.
`acting` not built yet	Acting rosters and auditions. `acting.manage` — Manage acting rosters and auditions. (not built yet)
`appeals`	Appeals and support intake. `appeals.review` — Open the review desk: read, assign, respond to and decide member cases. Includes working the ticket channels — closing, transcribing and reopening them. `appeals.panels` — Write and publish the ticket intake panels and the FAQ panels members read.

Some permissions imply others. Granting moderation.logsClear also grants moderation.logs — clearing a feed you cannot read is not a coherent permission. Anything in Moderation, Events, Sessions or Management also grants staff.panel, because those tools live inside the moderator panel and would otherwise be unreachable. The Permits page shows you this as it happens.

These surfaces stay owner-only and have no permission you can grant. Permissions — create or edit permits. Positions — appoint hub directors. Data & Privacy — export or erase server data. A permit that could edit permits could grant itself anything, and the owner would have no way to take it back.

If you previously used a single staff role, it was migrated automatically into a permit named “Staff” holding every action in Staff, Moderation, Faction Hub, Events and Sessions. Deliberately not Management. Permits saved under the older flat capability list were upgraded in place to the equivalent actions, so nobody lost access in the change.

Every setting

Setting	Default	What it does
Staff Hub	On	Moderator panel, shifts, lookup.
Faction Hub	On	Faction directory, rosters, applications.
Appeals & Support	Off	Case desk, ticket panels, FAQ panels and transcripts.
Roleplay / Acting	Off	Save, but nothing is built behind them yet.
Hub server	This server	Which Discord each hub runs in, if you split across servers.
Store message content	Off	Whether Discord message text is retained. See Your Data.
Bot nickname / avatar / banner	Unset	Per-server appearance for the bot.
Bloxlink API key	Unset	Enables Discord→Roblox lookups. Get a Server API Key from blox.link → Developer.
Game ingest key	Unset	Authenticates the in-game scripts. Shown once when generated.

Treat the game ingest key like a password. Anyone who has it can post join, leave and chat events into your server's logs. It is displayed exactly once when you generate it — if you lose it, regenerate rather than hunting for it, and update your game scripts. Never paste it into a public repository or a screenshot.

Message content logging

Off by default in every server. When enabled, Vortigern stores the text of messages sent in your server so they appear in the chat log — the most recent 300, each truncated to 500 characters. Turning it off stops new messages being stored immediately; it does not remove what was already collected, so use Erase Server Data if you want that gone too.

If you turn this on, tell your members. Depending on where they live, logging their messages without notice may breach privacy law. That obligation sits with you as the server operator, not with us.

This setting also requires the privileged Message Content Intent to be enabled for the bot in the Discord Developer Portal. Without it, Discord sends empty message text and chat logs will be blank even with the setting on.