UNITEDUnited Setup Guides
These guides explain decisions and workflows, not just commands. Start with the problem your server needs to solve, then use the linked command reference when you need exact syntax.
A practical first-hour checklist covering role position, permissions, Bot Logs, protection, tickets, and validation.
Build a Secure Discord ServerPermissions, role hierarchy, Bot Logs, Anti-Nuke, Anti-Raid, Anti-Spam, whitelists, and a safe rollout order.
Build a Support Ticket WorkflowTicket types, categories, staff access, questions, transcripts, lifecycle controls, and duplicate prevention.
Understand Logs and Incident RecoveryAudit attribution, log routing, snapshots, Incident Mode, repair choices, and what should be handled manually.
United DocumentationDetailed command-based setup and troubleshooting for every major United system.
A recommended learning order
- Start with the new-server guide to establish role position, permissions, Bot Logs, and a small test plan.
- Read the security guide before enabling automatic punishments. Discord role hierarchy and audit-log visibility determine whether enforcement can work.
- Build ticket types and staff access before publishing a panel. The public panel should be the final step, not the first.
- Use the incident and logging guide before pressing Restore. A snapshot comparison can describe a change without meaning the current server is broken.
- Keep the command guide open for exact arguments, aliases, and access requirements.
How these guides are maintained
United's public guides are maintained alongside the bot source and reviewed when behavior changes. They are based on the workflows implemented in United, including its shared message pipeline, ticket persistence, unified logging routes, permission checks, PostgreSQL runtime storage, and dashboard controls. They are not copied from another bot's documentation.
When a guide and the running bot appear to disagree, report the exact command, dashboard screen, server permission state, and resulting Bot Logs entry. That gives the developer enough information to reproduce and correct either the behavior or the documentation.