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.

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 with the Discord account that manages your server

Submitt uses Discord OAuth for account identity. Use an account that is the server owner or has Administrator/Manage Server permission. The Servers page only shows communities your logged-in Discord account is allowed to manage.

3. Install Submitt into Discord

Open Dashboard → Servers. Find the community you want to use and choose Add Submitt. Discord will open the bot installation flow for that specific server. Approve the requested permissions and return to Submitt 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 Dashboard → Servers, the server should show BOT INSTALLED. Choose Use server slot. The status changes to LICENSED, and configuration pages can now save server-specific settings.

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.

5. Complete Server Setup

Choose Setup beside the licensed server or open Dashboard → Setup. Submitt 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, select the server, and create a 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.