Whitelabel

Whitelabel is an add-on on top of Premium. The ticket system then runs under your own Discord application: members see your bot, with its name, avatar and status, in panels, tickets, DMs and the member list. The dashboard, your panels and every setting stay exactly as they are.

#Before you start

• The server needs Premium. Whitelabel is booked on top, per server.
• You need your own application in the Discord developer portal. You own it and its token, we run the bot for you.
• The bot needs the privileged intents Server Members and Message Content. Discord lets you turn them on freely while the bot is on fewer than 100 servers. Bigger bots need Discord's verification first.

#1. Create the application

1. Open the Discord developer portal (opens in a new tab) and create a new application. Its name becomes the bot's name.
2. Under Bot, set the avatar and banner if you like.
3. Under Bot · Privileged Gateway Intents, turn on Server Members Intent and Message Content Intent. Save.
4. Under Bot, turn off Requires OAuth2 Code Grant. With it on, the invite link does not work.
5. Under Bot, press Reset Token and copy the token. Discord shows it only once.

Treat the token like a password. Anyone with it can act as your bot. Never post it in Discord or send it to anybody.

#2. Connect it in the dashboard

1. Open your server in the dashboard and go to Whitelabel.
2. Paste the token and save. It is stored encrypted and never shown again, not even to you. If you lose it, reset it in the portal and paste the new one.
3. The page shows the state of your bot. After a few seconds it should say online.

#3. Invite your bot

Use the invite link the page shows. It asks for the same permissions as the shared bot, see Getting started. Keep all of them ticked.

Keep the shared Roleplay+ bot on the server as well. Only one of the two answers at a time, and the shared bot takes over again if you pause Whitelabel or Premium ends.

#4. Set the presence

Choose what members see next to your bot:

• Status: online, idle, do not disturb or invisible.
• Activity: playing, watching, listening, competing, a custom text or none, with a text of up to 128 characters. Watching tickets is the default.

#5. Name and avatar

You can change your bot's name and avatar from the dashboard as well, without opening the developer portal. Discord allows two username changes per hour. A third change in that hour fails until the hour is over.

#6. Resend all panels

Buttons and menus belong to the bot that sent the message. Panels sent by the shared bot keep pointing to it, even after the switch. Press Resend all panels: your bot posts every known panel again and the old messages are deleted.

Buttons in older messages, for example in tickets that were open before the switch, still belong to the old bot. If one of them does not react, use the matching command instead, such as $close.

#One bot for several servers

One application can serve several of your servers. Each of them needs its own Premium and its own Whitelabel add-on. Invite the same bot to each server and connect it on each server's Whitelabel page.

#Pause or remove

• Pause switches the server back to the shared bot. Your token, presence and settings stay stored, so you can switch back later.
• Remove deletes the stored token and switches the server back to the shared bot.
• After both, press Resend all panels again, so the panels belong to the shared bot.
• When Premium ends, the server falls back to the shared bot on its own. Resend the panels then too.

#Limits

• Requires Premium on the same server. Without Premium, the server uses the shared bot.
• The application is yours. If you delete it, reset its token or turn off an intent, your bot goes offline until you fix it on the Whitelabel page.
• Panels must be resent after every switch between your bot and the shared bot.
• Discord allows two username changes per hour.

#Troubleshooting

#The state says invalid token

Discord rejected the token. It was reset in the portal, copied only partly, or the application was deleted. Reset the token in the portal, copy it in full and paste it again.

#The state says disallowed intents

Discord refused the connection because Server Members Intent or Message Content Intent is off. Turn both on under Bot · Privileged Gateway Intents, then save on the Whitelabel page so the bot connects again. If your bot is on 100 or more servers, Discord has to approve the intents first.

#The bot is online but nothing happens

The bot is probably not on the server yet. Invite it with the link from the Whitelabel page. If Discord shows an error during the invite, check that Requires OAuth2 Code Grant is off.

#Members still see the shared bot

The panels were sent before the switch. Press Resend all panels.