Discord Guilds

The Discord Guilds view is the admin registry of every Discord server (guild) that has the Lumio Discord bot installed and is linked to a Lumio account. It exists so operators can audit the full set of guild-to-account mappings and forcibly unlink a guild when support cases require it.

Where to find it

Admin sidebar → Discord Guilds (/discord-guilds).

Quick start

1. Open Admin → Discord Guilds.
2. Scan the table for the guild in question.
3. To detach a guild from its account, click the red trash button on the row.
4. Confirm the prompt. The mapping row is removed and the bot's association with the guild is dropped.

Detailed walkthrough

Guilds table

Columns:

• Guild - the guild's Discord icon (or an initial avatar) plus the guild name as reported by Discord. A Bot removed badge appears next to the name when bot_removed_at is set; the server settings remain while the bot is absent.
• Guild ID - Discord snowflake ID, in a monospace badge.
• Account - linked Lumio account name plus the first 8 characters of its account ID. It is plain text, not a link.
• Connected At - the date the link was established.
• Actions - a red trash button, gated on discord-guilds:delete.

A count header reads "{N} guild connection(s)".

The table is not sortable, searchable, or paginated - every mapping is rendered in one list.

Deleting a connection

Clicking the trash button raises a native browser confirm ("Are you sure you want to delete this guild connection?"). Confirming removes the mapping row via the admin mutation. The Discord bot remains a member of the guild itself - you have to remove the bot from the Discord server separately if you want it out of the guild.

Bootstrapping guild mappings

Guild connections are created under Connections → Discord in the user dashboard. The verified OAuth invite uses authorizeBot(platform: "discord") or GET /v1/bot-connections/discord/authorize, returns through /api/connections/oauth/discord/callback, and stores the server ID confirmed by Discord. There is no "create guild connection" button in the admin UI - it is list-and-delete only.

Common scenarios

• Lost admin of a Discord server - the Lumio-owning user left and can no longer manage the bot. Delete the guild connection; the remaining server admins can re-invite the bot under a fresh account.
• Bot removed from Discord - the mapping is marked, with settings preserved. The original account can reconnect it. A verified invite by another account can take over a marked server; the old account's settings are cleared.
• Account dissolution - when closing an account, remove any remaining guild connections to stop the bot from responding in those servers.
• Duplicate mapping - if the same guild snowflake appears twice (shouldn't happen, but theoretically), keep the newer row and delete the older.
• Audit - read the Connected At column to spot recent onboardings; the column is not sortable, so scan it by hand.

Permissions

Action	Permission
View guild connections	discord-guilds:read
Delete a guild connection	discord-guilds:delete

Dashboard entry requires admin:access. System admins hold both implicitly.

API

UI action	GraphQL	REST
List guild connections	adminDiscordGuilds	GET /v1/admin/discord-guilds
Delete guild connection	adminDeleteDiscordGuild	DELETE /v1/admin/discord-guilds/\{guild_id\}

Tips & gotchas

• The delete action only clears Lumio's DB row. To remove the bot from the Discord server itself, a Discord server admin has to kick the bot (or the bot owner can do it from the Developer Portal).
• Guild connections are keyed by Discord snowflake (guild ID), not by account. An active mapping cannot be taken over by another account; a marked, bot-removed mapping can be taken over through a verified invite.
• There is no rename / re-account UI. To change ownership, delete and re-invite.
• The Discord bot token is not set in the admin panel. The Discord bot reads it from DISCORD_BOT__BOT__TOKEN; the server invite app comes from [auth].discord_bot_client_id / discord_bot_client_secret in the API configuration (see Providers).

Related

• Providers - provider kill-switches and where the Discord bot is configured
• Bot Control - pause / resume the Discord bot per account
• Bot Commands - Discord slash commands and prefix commands