White Label
White Label lets a licensed server run Submitt through a Discord bot application owned and branded by that customer. Submitt still hosts, updates and operates the backend; the customer's bot becomes the Discord identity members see.
Standard vs White Label
Install the official Submitt Discord bot, assign the server license, and configure tickets, applications, moderation and automation from the dashboard. Discord actions are performed by the Submitt bot account.
Assign the licensed server, connect a customer-owned Discord bot application, invite it to that server, and activate White Label. Discord actions are then performed by the customer's bot identity while Submitt remains the managed backend.
What the customer owns
The customer creates the Discord application in Discord Developer Portal and controls its bot username, avatar, application description and Discord-side identity. The customer does not receive Submitt source code and does not need to host a separate copy of Submitt.
What Submitt continues to manage
Submitt remains responsible for the dashboard, database, licensing, hosting, updates, ticket and application workflows, moderation, automations, transcripts, analytics and the persistent Discord connection. The custom bot is the Discord identity connected to that managed infrastructure.
Feature parity with Premium
White Label keeps the same core Submitt feature set as Premium: tickets, applications, independent moderation modules, Incident Reports, command readiness and staff-role access, /submitthelp, role-based community dashboard access, workflow automation, SLA processing, analytics, audit history and secure visual transcript viewing. The plan difference is the Discord identity and public-facing branding, not a reduced or separate workflow engine. The status command is /botstatus on White Label instead of /submitt.
Dashboard delegation works the same on Premium and White Label. The Discord server owner may grant selected Discord roles access to selected community-dashboard sections. Billing, server licensing and White Label bot credentials/activation remain restricted to the Submitt subscription owner, while Dashboard Access policy itself remains restricted to the Discord server owner.
Set up a White Label bot
Never post a Discord bot token in a ticket, chat, screenshot or public repository. Submitt encrypts the token before storing it and does not display the saved token back in the dashboard. If a token is ever exposed, reset it in Discord Developer Portal and reconnect the new token.
Each licensed White Label server uses its own Discord application and bot token. This keeps command registration, permissions, presence, runtime health and server isolation independent. Submitt prevents the same custom Discord application from being assigned to multiple White Label servers.
What changes after activation
New Discord operations for that licensed server are routed through the customer's custom bot. This includes launcher publishing, dashboard-triggered role and moderation actions, Application decision messages, Incident Report processing, slash commands, ticket/application interactions, automations and other Discord-facing workflows. Stored tickets, Applications, transcripts, settings and history remain in the same Submitt database.
The official Submitt bot may remain installed as a passive standby. While White Label is active, runtime routing prevents that standby from processing interactions, ticket events or moderation events, so the two bot identities do not compete. Keeping the standby installed makes a future Premium downgrade seamless.
If existing launcher messages were originally posted by the official Submitt bot, Submitt replaces or republishes those launchers through the custom bot during activation because Discord does not let one bot edit another bot's messages. This migration includes Ticket launchers, Application launchers, and Reaction Role panels so buttons and select menus always belong to the bot identity that is currently active.
Recent ticket improvements are shared by both plans: Ticket editor saves run in place without wiping other unsaved fields, launcher changes can update the existing Discord message, and ticket closure uses one clean closure/transcript embed with a secure View Transcript link instead of exposing raw HTML source.
Bot status and presence
The bot username and avatar are controlled in Discord Developer Portal. The White Label dashboard also lets the customer configure an optional Playing, Watching, Listening or Competing status. Connection state and actionable setup errors, including missing privileged intents or invalid credentials, are shown on the White Label page.
Brand appearance and attribution
White Label includes optional embed appearance controls for display name, accent color, logo, author, thumbnail and banner. These settings style Submitt-generated content and are separate from the actual Discord bot username and avatar.
Every Submitt-generated White Label embed displays Powered by Paradise Utilities in its footer. Customers cannot remove, hide, replace or customize this attribution. White Label changes the Discord bot identity and community presentation; it does not remove credit for the underlying Paradise Utilities platform.
Deactivating or downgrading
Deactivating White Label stops the custom Discord runtime but preserves its configuration unless the customer explicitly disconnects it. If the official Submitt standby is installed, it becomes the fallback identity and Submitt republishes managed Ticket, Application, and Reaction Role launchers through the official bot so interactive buttons and menus remain usable. Stored configuration and historical records are not erased by the identity change.
Before scheduling White Label → Premium, Submitt requires the official bot to be installed as a standby on every affected server. At the plan boundary, Submitt retires Ticket, Application, and Reaction Role launcher messages owned by the custom application, disables the custom runtime and republishes those launchers through the official bot. If a plan is changed externally without a standby, Submitt temporarily keeps the custom bot active and flags the server for handoff instead of taking the community offline immediately.
Disconnecting a custom bot
Disconnecting is available only while the custom bot is deactivated. It removes the saved encrypted bot token and White Label bot connection from Submitt. It does not delete the customer's Discord application from Discord Developer Portal and does not delete Submitt history.