DOCUMENTATIONSubmitt customer documentation
This guide is written for Discord server owners, administrators and staff managers using the Submitt dashboard and bot. It explains not only what each feature does, but the recommended order to configure it, what your members will see in Discord, and what to check when something does not behave as expected.
How Submitt is designedThe dashboard is the control center. You build and manage configuration on the website; the Submitt bot carries that configuration into Discord. You should rarely need to configure the product through bot commands.
Choose a guide
Getting startedGo from a new subscription to your first live ticket or application panel.Dashboard guideLearn what every dashboard section controls and when to use it.Dashboard accessGrant selected Discord roles limited access to specific community dashboard sections while keeping ownership controls private.Servers & setupInstall Submitt, assign a license slot, configure staff defaults and pass health checks.TicketsBuild support Tickets with staff workflows, transcripts, questions, tags and satisfaction surveys.FormsCreate Discord forms with private response channels, priorities, closing, transcripts and Combined Panels without creating Tickets.ApplicationsCreate Discord-native application forms, eligibility rules, review stages and role actions.CommandsSee command readiness from the owning module, manage staff command role access and understand /submitthelp.Server ModulesConfigure welcome and goodbye messages, Auto Role, AutoMod, member screening, raid protection, Auto Slowmode and Discord logs.Workflows & analyticsConfigure SLAs, automations, saved replies, tags and operational reporting.White LabelCustomize eligible servers while understanding what branding can and cannot change.Billing & licensingManage embedded checkout, server slots, payment methods, plan changes and invoices.Operations & dataMonitor health, control retention, export data and understand destructive cleanup tools.TroubleshootingResolve installation, permission, role, billing, panel and Discord connection problems. The normal customer journey
01SubscribeChoose Premium or White Label for one or three Discord servers and complete payment inside Submitt.
02Connect DiscordSign in with the Discord account that owns or can manage the communities you want to configure.
03Install and licenseAdd the Submitt bot to Discord and attach the server to an available subscription slot.
04Pass setup checksConfirm bot health, permissions, role hierarchy and default staff settings before publishing panels.
05Build workflowsCreate ticket panels and application forms, then configure commands and server modules and publish member-facing workflows directly into Discord.
06Operate and improveUse analytics, SLAs, automations, transcripts, audit logs and staff tools as your community grows.
Important terms
Licensed serverA Discord community assigned to one of the server slots included in your active Submitt subscription.
PanelA message published by Submitt in Discord that members use to open a ticket or begin an application.
Ticket typeAn option inside a ticket panel, such as General Support, Player Report or Management Contact.
Standalone FormA structured Discord intake workflow that creates a private response channel with priority, closing and transcript support without creating a Ticket.
ApplicationA reviewed workflow with eligibility, stages, decisions and optional role actions.
WorkflowAn SLA, automation, saved reply or tag that helps staff process support consistently.
EntitlementThe active plan permissions that determine server-slot count and whether White Label branding is available.
Recommended administrator routine
After initial setup, most owners spend their time in Tickets, Applications, Commands, Modules and Workflows. Review Analytics to identify delays, Operations to verify service health and retention settings, and Audit Log when you need to determine who changed an important configuration. Billing and server licensing normally require attention only when changing plans, payment methods or licensed communities.
