Servers & setup
A stable Submitt installation depends on three things being true at the same time: the bot is in Discord, the server is attached to a valid subscription slot, and Discord permissions/role hierarchy allow the bot to perform the actions you configure.
Understanding installation vs licensing
The Submitt bot account has been added to the Discord guild.
The guild is consuming one of the server slots included with your active Submitt plan.
The bot is online, has the required permissions and can manage configured automation roles.
The owner has saved required defaults and Submitt's critical health checks are passing.
Install the bot from the Servers page
Sign into Submitt with Discord, open Dashboard → Servers, locate the guild and click Add Submitt. The install button is generated for that specific guild so you do not need to manually construct an invite URL.
When Discord asks you to authorize permissions, approve the permissions required by the product. Removing permissions later can break ticket channel creation, message publishing, transcripts or role automation even if the dashboard still remembers the configuration.
Assign and release server slots
After installation is detected, click Use server slot. A one-server subscription can have one linked guild; a three-server subscription can have up to three. If you release a slot, the subscription remains active and the slot becomes available for another manageable Discord server.
Releasing the license disables new licensed activity for that guild. Review active tickets/applications and export anything you need before moving the slot to a different community.
Readiness checklist
The Setup page scans the selected server and shows each condition separately. A green/complete item means the latest health scan sees that requirement as satisfied. If the heartbeat is stale, the dashboard may temporarily show warnings even though the bot is installed; confirm the bot host is actually running.
Required Discord permissions
Submitt needs enough permission to publish panels, create private ticket channels, create/manage private threads, manage channel permission overwrites, send messages in channels/threads, embed links and interact with the workflow you configure. The Setup page reports missing permissions instead of silently failing later.
Avoid granting Administrator merely to hide a permissions problem if your community uses a stricter permission model. It is better to grant the required permissions intentionally and confirm the health check passes.
Discord gateway intents
Enable both Message Content Intent and Server Members Intent for the Submitt bot in the Discord Developer Portal. Message Content is used for complete ticket transcripts and message-based moderation such as anti-spam, duplicate-message, mention, invite and link filtering. Server Members is used for private Thread Mode staff access plus join automation such as Auto Role, welcome messages, prohibited-name checks and minimum-account-age protection.
Role hierarchy
Discord prevents bots from adding/removing roles that are positioned above the bot's highest role. If an application is supposed to grant Member, LEO or Staff roles, drag the Submitt role above every role it must manage. The Setup health scan checks configured application automation roles and warns when the hierarchy would prevent the action.
Default staff role and logging defaults
Select a sensible default staff/support role during setup. Individual ticket/application workflows can be more specific, but the default gives new workflows a predictable baseline. Configure a default log channel if your server wants centralized operational records.
What to do when the bot is installed but shows offline
The dashboard health record depends on a heartbeat from the running bot service. Confirm the bot hosting process is online, the Discord token is valid, the bot and Render web service point to the same MySQL database, and the guild has not removed the bot. Restarting the bot host is appropriate if the process has stopped; reinstalling the Discord application usually is not necessary.
Multiple servers
Configuration is isolated by guild. A ticket panel created for Server A does not appear in Server B, even when both belong to the same customer subscription. Always verify the active server selector before creating, editing or deleting configuration.