White label

With the White Label plan, players see your bot, your domain and your name. Modhelm runs in the background. This page walks you through creating your own Discord application and connecting it.

What you get

• Your own bot: your name, your picture, your application. Cards, panels and direct messages come from it.
• Your own domain for the portal and verification, see Portal and custom domain.
• No "Powered by Modhelm" in the portal, on cards and in direct messages.
• Your legal pages everywhere players look, including /help in Discord.

Before you start

• The White Label plan on this server.
• A Discord account that will own the application. For studios, a team account or the owner's account is best, because the application cannot be transferred later without Discord's consent.
• Your custom domain set up and active, so players see your address. The Discord sign in itself runs through modhelm.com and then returns to your domain.

Step 1: Create the Discord application

1. Open the Discord Developer Portal and click New Application.
2. Name it the way players should see it, for example your game's name. Accept Discord's terms.
3. Under General Information, upload your icon and write a short description. This is what players see on the bot's profile.

Step 2: Create the bot and turn on the Server Members intent

1. Open the Bot tab.
2. Click Reset Token, confirm and copy the token. Discord shows it only once.
3. On the same page, under Privileged Gateway Intents, turn on Server Members Intent. Modhelm needs it to react when members join, for automatic verification.
4. Leave Public Bot on or off as you like. If it is off, only you can invite the bot.

Applications in fewer than 10,000 unique users can turn this intent on themselves. Larger bots need Discord's intent review, which applies to very few single community bots.

Step 3: Copy the OAuth2 credentials and add the redirect

1. Open the OAuth2 tab.
2. Copy the Client ID (this is the same as the Application ID) and the Client Secret. Reset the secret if it has never been shown.
3. Under Redirects, add exactly this address:

https://modhelm.com/api/oauth/discord/callback

Use it as it is, with https:// and the path, even though your portal runs on your own domain. When a player signs in on your domain, Discord shows your application's name and icon, sends the player to modhelm.com for a moment and Modhelm brings them straight back to your domain. Your domain never needs a redirect entry of its own.

Step 4: Enter your legal links

Discord's Developer Terms require every application to link a privacy policy and terms of service. Under General Information, fill in:

• Privacy Policy URL: your privacy policy, for example https://appeals.yourgame.com/privacy
• Terms of Service URL: your terms, for example https://appeals.yourgame.com/tos

On your own domain these two addresses show the pages you entered under Settings > Portal > Legal pages. You are the owner of the application, so these have to be your documents, not ours.

Step 5: Connect the bot in the dashboard

1. In the dashboard, open White label.
2. Enter the Application ID, the bot token and the client secret.
3. Click Connect bot. Modhelm checks the token, stores token and secret encrypted and starts your bot within a few seconds. The page shows its status: Starting, Online, Token rejected or Turned off.

Token and secret are never shown again. If you ever need to change them, click Replace bot.

Step 6: Invite your bot and remove the Modhelm bot

1. Copy the invite link from the White label page. It already contains the permissions the bot needs.
2. Invite your bot to the server.
3. Once your bot is online in the server, remove the Modhelm bot. From now on only your bot reacts in this server.
4. Post the panels again under Settings > Channels & roles, so they come from your bot.

Slash commands, cards and direct messages now carry your bot's name and picture.

Step 7: Hide the Modhelm branding

Under White label > Branding, turn on Hide "Powered by Modhelm". This removes the note from the portal, the cards and direct messages. /help shows your legal links instead of ours.

Who owns what

• The Discord application belongs to you. Modhelm operates it on your behalf as a service provider, which is covered by the data processing agreement you accepted.
• Credentials are used only for your application and are stored encrypted. You can delete them any time with Remove bot; the server then switches back to the Modhelm bot.
• Verification stays network wide. Members who verify through your bot are verified with their Discord user ID, which is the same in every application.

Limits of a white label bot

• It runs on Modhelm's infrastructure together with other bots. Outages are shown on the status page.
• The /premium command is not available in white label bots. Plans are managed on the website.
• Discord shows an "APP" badge on every bot. That cannot be hidden.

Troubleshooting

• Token rejected: the token was reset in the Developer Portal or copied incompletely. Reset it and enter the new one.
• This token doesn't belong to the application ID you entered: Application ID and token come from different applications.
• Verification on your domain fails or Discord says Invalid OAuth2 redirect_uri: check the redirects in the OAuth2 tab. https://modhelm.com/api/oauth/discord/callback has to be there exactly. An older entry with your own domain does no harm, but it is no longer used.
• Members do not get the role on join: the Server Members Intent is off. Turn it on under Bot and restart the bot with Replace bot or by removing and connecting it again.