> For the complete documentation index, see [llms.txt](https://vampauth.gitbook.io/vampauth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vampauth.gitbook.io/vampauth-docs/integrations/discord/panels.md). # Create and manage a panel The main Vampauth bot uses a private guided menu. Run `/panel` in your server. ## Before setup You need **Manage Server**, a linked Vampauth account, and ownership of the chosen project. Link your Discord account in Vampauth Settings; `/login` checks the association. The bot needs View Channel, Send Messages, and Read Message History in the destination. An optional member role also needs Manage Roles. The role must be non-managed, non-administrator, and below the bot's highest role. ## Create a panel Choose **Create panel**, select your project and a connected loader, choose the channel, optionally set a role/title, then preview and publish. A project can have several panels in one server. Each panel selects one stable loader ID; saved keys belong to the project and work across its panels. ## Manage or repair Under **Manage panel**, select a panel to edit its settings or loader, browse members/keys, move it, or delete it with confirmation. **Refresh / repair** updates the existing message or restores a confirmed deleted one. **Move to channel** publishes the same panel in the new channel and removes its old message. Fix missing permissions first; a network/access error isn't treated as proof that a message was deleted. Published panels and saved keys survive bot restarts. Private menus and unpublished previews expire after five minutes or a restart; reopen `/panel`. Deleting a panel doesn't delete saved project keys or remove roles already granted. Rotating a loader URL doesn't require recreating the panel. If its selected loader is deleted or disconnected, choose another explicitly; the bot won't silently substitute one. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://vampauth.gitbook.io/vampauth-docs/integrations/discord/panels.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.