Getting started
This guide takes a brand-new Submitt customer from purchase to a live Discord workflow. Complete the steps in order; doing so prevents most permission, role hierarchy and licensing problems before members ever see a panel.
By the end of this guide, one Discord server will be licensed, its health checks will pass, and you will have published either a ticket panel or application panel.
1. Purchase the correct plan
Open the Pricing page and choose the plan that matches the number of Discord communities you need. Premium and White Label both include the full ticket/application feature set; the difference is branding. One-server plans license one community at a time, while three-server plans license up to three.
Checkout happens inside Submitt using Stripe. Card information is handled securely by Stripe Elements, while the surrounding checkout experience remains on the Submitt website. After payment succeeds, provisioning is confirmed through Stripe webhooks rather than relying on the browser success page.
2. Sign in and choose your server
Submitt uses Discord OAuth for account identity. Use an account that is the server owner or has Administrator/Manage Server permission. After verification, Submitt opens the Server Selector. Licensed servers appear at the top; other manageable communities appear underneath.
Do not create another Submitt account. Refresh the Server Selector or reconnect Discord and confirm the account you are using actually has Manage Server, Administrator or ownership access.
3. Install Submitt into Discord
From the Server Selector, find the community you want to use and choose Add Submitt. Discord opens the bot installation flow for that specific server. Approve the requested permissions, return to the selector and refresh the list after the bot appears in your member list.
Installing the bot and licensing the server are separate actions. Installation places the bot in Discord; licensing tells Submitt which paid server slot that guild should consume.
4. Assign a subscription slot
Back on the Server Selector, the server will show Submitt as installed. Choose Assign License. The server moves into the Licensed Servers section and can immediately be selected for setup and configuration.
If all slots are already used, release a server you no longer need or upgrade to a plan with additional slots. Releasing a slot does not cancel your subscription.
The Launch Checklist follows the server selected in the dashboard. Bot installation, setup readiness and first-workflow progress from another licensed server do not count toward the current server.
5. Complete Server Setup
Choose the licensed server from the selector, then open Server Setup. Submitt remembers that server selection across the dashboard and checks the live bot heartbeat, required Discord permissions and role hierarchy before allowing setup to be marked complete.
6. Create your first ticket workflow
For the fastest test, open Dashboard → Tickets for the selected server and create a Ticket Panel. Give it a clear internal name such as “Main Support”, choose the Discord channel where the panel should be published, then add at least one ticket type such as General Support.
Add intake questions if staff need information before a ticket channel opens. Keep the first test simple: one ticket type, one or two questions, and one staff role. Publish the panel, then click it yourself in Discord to verify channel creation and staff access.
7. Or create your first application workflow
Open Dashboard → Applications and create a form. You can keep it as a single application or add application types such as Civilian and LEO. Each type can have its own questions, approval role, approval DM and denial DM. Publish one panel; when a member clicks Apply, Submitt lets them choose the path and then opens the correct questions directly on their Discord screen.
8. Test as both a member and staff user
Before announcing the system publicly, test the complete experience. Create a ticket from a non-staff account if possible, claim it as staff, change priority, add a note, close it and confirm the transcript. For applications, submit a test application and verify that reviewers can claim it, change stages and make a final decision.
9. Finish operational configuration
Once the basic flow works, configure SLAs, automations, saved replies and tags, review retention and export settings, and configure White Label branding if your plan includes it.
Build one complete workflow and test it before creating many panels. Once the first workflow behaves correctly, duplicate the same staff-role, permission and naming conventions across the rest of your server.