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
- Open Admin → Discord Guilds.
- Scan the table for the guild in question (sort by recently connected or by account).
- To detach a guild from its account, click Delete on the row.
- Confirm the prompt. The guild row is removed and the bot's association with the guild is dropped.
Detailed walkthrough
Guilds table
Columns:
- Guild — guild name as reported by Discord when the bot joined.
- Guild ID — Discord snowflake ID, monospace.
- Account — linked Lumio account (click-through to
/accounts/\{id\}). - Connected At — timestamp the link was established.
- Actions — red Delete button.
A count header reads "{N} guild connection(s)".
Deleting a connection
Clicking Delete shows a confirmation dialog ("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 end-user-side: a user adds Lumio's bot to their Discord server via OAuth invite; Lumio stores the mapping. 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.
- 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 — sort by Connected At to see recent onboardings.
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. Re-inviting the bot from a different Lumio account will create a new mapping only if the old one is deleted first.
- There is no rename / re-account UI. To change ownership, delete and re-invite.
- The Discord global bot token is configured on Providers, not here.
Related
- Providers — Discord global-bot configuration and credentials
- Bot Control — pause / resume the Discord bot per account
- Bot Commands — Discord slash commands and prefix commands