← All documentation

Bot & webapp staff

Admin Workspace

Manage system settings, staff access, Chronicles, and records from one permission-controlled workspace.

Checked against the live application ·

Open the workspace

  1. Sign in with Discord using an authorized staff account.
  2. Open Profile → Admin Workspace.
  3. Choose a horizontal tab, then expand the numbered categories you need. Users, Chronicles, and database records include search and exact field filters.

Bot Staff and Webapp Staff inherit operational workspace permissions. Chronicle staff roles alone do not grant system-wide access. The site owner can override each person's workspace permissions.

Back to top ↑

Change settings

  1. Open System settings and select a category.
  2. Adjust the controls, enter a reason, and save.
  3. Use Activity to inspect the recorded changes. If another administrator saved first, reload and review the newer values before trying again.

System settings control notices, default themes, registration, application intake, character limits, homebrew intake, dice availability, project proposals, and Discord presence and notifications. Website settings apply to subsequent requests; bot presence refreshes within about a minute.

Back to top ↑

Configure Chronicle defaults

Chronicle defaults supply the initial configuration for new servers. They do not rewrite existing Chronicle configurations or accepted character rules. Discord role IDs, channel IDs, and server-specific text are configured in each Chronicle.

  1. Choose Chronicle defaults, select a category, and save the desired baseline.
  2. For an existing server, open Chronicles, inspect its record, and choose Edit Chronicle settings.
  3. Use the normal Chronicle preview and save process. The configuration history identifies the administrator who saved each revision.
Back to top ↑

Manage users and staff access

Account moderation permits profile corrections and suspension of ordinary accounts. Only the site owner can change staff roles and workspace permissions. Owner accounts are protected from this editor.

  1. Open Users & staff and search for the account.
  2. Choose Inspect, then Edit account or Staff access & roles.
  3. For a workspace permission, choose the staff default, Allow, or Deny. Review the account's existing bot and website permissions separately.
  4. Enter a reason and save. Brewer and Storyteller applications continue to use the independent review workflow.
Back to top ↑

Inspect database records

The explorer groups tables by accounts, Chronicles, characters, play, Codex foundations, Vampire, Werewolf, rules, sources, Brewery, and operations. Open a table to search, filter, paginate, and inspect its structure.

Inspect shows field labels, readable choices, Yes/No values, structured data, and links to related records. Related records opens the corresponding filtered table. Large field displays are capped; the interface does not provide raw SQL or direct row editing.

Passwords, session contents, OAuth secrets, and similar credentials are protected. Research imports and unreviewed source prose are not published through the explorer. Publication, character review, progression agreements, and XP accounting continue to use their dedicated workflows.

Authorized staff can edit catalog configuration such as game availability, names, and navigation ordering from a record's Edit catalog configuration button. Engine identifiers and published rules are not changed by that editor.

Back to top ↑

Check operations and activity

Operations shows database connectivity, pending migrations, the Discord heartbeat, deployment security status, and delivery queues. Activity records workspace settings, account changes, access changes, and inspected records. Chronicle revisions and gameplay audit tables remain available through their own records.

VPS credentials, process restarts, certificates, and host configuration remain deployment-managed. Pausing application notices retains queued work; enabling delivery resumes processing.

Back to top ↑