Whitelabel bot
Run SUPREO under your own bot's name and avatar — a dedicated instance for your server, with its own presence.
Do this on my dashboardBy default your server uses the shared SUPREO bot. With the Whitelabel bot add-on, SUPREO runs a dedicated instance under a Discord application you own: your name, your avatar, your status line — and no SUPREO signature on its messages. It is also what makes DM tickets possible, since members message your bot directly.
Premium
Set it up
Create the application
In the Discord Developer Portal, press New Application, name it, and open Bot. Set the name and avatar members will see.
Under Privileged Gateway Intents, tick Message Content Intent and Server Members Intent, then Save Changes:
- Message Content is required. Without it every message reaches the bot empty: no transcripts, no DM tickets, and the scam-picture filter cannot see pictures.
- Server Members powers what happens when someone joins: welcome cards, auto roles, verification and the humans and bots stat counters. Without it the bot still starts, with those features off. The Welcome page then shows a warning; once you have ticked the intent, press I ticked it — check again there.
What each intent is used for, in detail, is in Privileged intents.
Copy the token and the application ID
Bot → Reset Token shows the token once — copy it. General Information → Application ID is the other value you need.
Never share the token. SUPREO encrypts it at rest (AES-256) and never sends it back to the browser.
Save it on the dashboard
Bot Settings (sidebar → Advanced): paste the Discord bot token and the application ID, then Save Token.
Invite your bot and start it
Invite Bot opens Discord's authorise dialog for your application with the permissions SUPREO needs; add it to this server. Then press Start. The Process status turns Online within a few seconds, with the process id, restarts and uptime.
All settings — tickets, roles, welcome, verification — apply to this bot exactly as they did to the shared one. Panels posted by the shared bot keep working as long as it stays in the server; once you remove it, post your panels again from Ticket Panels so your bot owns the messages.
Presence
Bot presence sets the status (Online, Idle, Do Not Disturb, Invisible) and an activity — Playing, Watching, Listening to, Competing in, Streaming or a Custom status — with its text. It is applied when the bot starts; Restart applies it immediately.
Command permissions
Discord lets a member change your bot's command permissions only through your bot's own application. To do it from Command permissions, set this up once in the Command permissions card:
- In the Discord Developer Portal, open your bot → OAuth2. Under Redirects, add the URL shown in the card, then Save Changes.
- On the same page, copy the Client Secret (Reset Secret if you don't have it) and paste it in the card. Discord checks it before it is kept; it is stored encrypted.
- Each manager clicks Authorize your bot once on the Command permissions page, with the Discord account they use on the dashboard.
Remove the secret forgets it and every manager's authorization. Replacing the bot with another application does the same.
Start, stop, restart
The three buttons manage the bot process. Restart is what to press after changing intents in the Developer Portal. If the process shows Errored, the token is usually wrong or was reset — save a new one.
When the add-on ends
Premium and the Whitelabel Bot add-on are two subscriptions, each with its own renewal date (the Billing page shows both). Your bot runs while both are active.
- The add-on ends (cancelled at the end of its period, a failed payment, a refund): the bot is stopped and goes offline, and Start and Restart stay locked. Your token and settings are kept: renew the add-on from Billing, then press Start.
- Premium ends but the add-on is still paid for: the bot is stopped too, and the add-on keeps billing. Billing says so; renew Premium, or cancel the add-on from Manage Subscription. When Premium is back, the bot starts again by itself — unless you had stopped it yourself.
Danger zone
Delete Whitelabel Bot stops the process and permanently deletes the stored token. Your settings are kept; the server goes back to the shared bot.
Once your server passes 10 000 members
Discord then asks you to justify the two privileged intents in a review form. It is a form about SUPREO, not about you, so every answer is written out in Privileged intents application. You get 90 days, and the bot keeps working meanwhile.
Updating the token
If you reset the token in the Developer Portal, paste the new one under Update Bot Token and restart. The stored token is never shown.
Switching to another application
A token from a different application is a different bot: it starts with no intents and no permissions, whatever the old one had. Before you press Restart:
- In the Developer Portal, tick both privileged intents on the new application (Create the application).
- Save its token and its application ID under Update Bot Token.
- Press Invite Bot and add it to this server — and to your support server too, if DM tickets are routed there. Keep the permissions the dialog asks for.
- Remove the old bot from your servers.
The Bot Settings page checks the bot's permissions on both servers, category by category, and lists anything missing with a button to invite it again. The overview shows the same warning while something is missing. If the new bot still lacks a permission when a member opens a ticket, the member is told the ticket could not open, and the server's owner gets a DM from the bot listing the missing permissions, with a button to invite it again.