Token
Bot token is required for live bridge access
BotForge uses the token to let the connected bot read servers and execute allowed Discord actions. Tokens should be regenerated if they were ever exposed publicly.
Security & Permissions
Clear controls before BotForge touches a server.
Customers need to know exactly what the site can do. This page explains token usage, Discord permissions, confirmation prompts and audit visibility.
Permission model
Discord
Server access follows the bot
A server appears only when the bot is present there and the bridge can read it. Admin-level actions still depend on Discord permission and role hierarchy.
Confirm
Risky actions require yes/no approval
Kick, ban, delete, role edits, channel changes and competition deletion are treated as explicit-confirm actions.
Logs
Actions should be auditable
Admin workflows are structured so each change can record actor, target, bot, server, module and result.
Least exposure
Public pages do not expose admin controls
The live competition hub publishes player-facing data while admin actions remain inside the authenticated dashboard.
Recovery
Disconnect and rotate anytime
Owners can remove a bot profile, update a wrong token and rotate credentials from Discord when needed.