Skip to main content
Userplay posts through the shared Userplay bot by default. It works out of the box and needs nothing beyond adding it to your server. If you already have an established community, you can post through a bot you own instead. Your members see your studio in the member list and on every message, and you decide what the bot is allowed to do.

​
Which one is right for you

The rest of Userplay works the same either way. Playtests, announcements, surveys, waitlists, NDAs and key vaults all post through whichever bot you have chosen, and both bots reach your server the same way.

​
Setting it up

You can choose your own bot from the start. Go to Integrations → Discord → Connect, pick Your own bot, and the setup walks you through the rest. You will need a couple of minutes and an account on Discord’s developer portal.
1

Create an application

Go to Discord’s developer portal and create a new application. Give it the name and avatar you want your community to see, since this is exactly what they will see.
2

Copy the bot token

Open the Bot page and choose Reset Token, then copy it. Discord shows a token once, so copy it before leaving the page.
3

Paste it into Userplay

Paste the token into the setup. We check it with Discord and show you the bot it belongs to.
4

Add our redirect URL

Userplay shows you a URL to copy. Open your application’s OAuth2 page in Discord, add it under Redirects, and save. Then choose I’ve added it and we confirm it with Discord before moving on.This is what lets Discord send you back to Userplay after you add the bot, and tell us which server you picked. It is the only setting on your application you need to change.
5

Add the bot to your server

Choose Add to your server. Discord asks which server and which permissions, then brings you straight back here, connected.
That is the whole setup. There is no client secret to copy and no privileged intents to enable.

​
If you stop partway

Your token is saved as soon as we have checked it, which is before the bot has been added to any server. Leaving at that point is fine and nothing is lost. Until the bot is in a server, Userplay cannot post, so the Discord row does not count as connected. It shows what is left to do and takes you back to the step you stopped on.

​
What we ask for

The bot is added with three permissions: view channels, send messages, and embed links. That is the same set the Userplay bot uses, and it is everything needed to post an announcement. Your token is encrypted before it is stored, and it is never shown again after you save it. You will only ever see its last four characters. If you want to rotate it, reset the token in Discord and paste the new one.

​
Changing things later

Your bot and your server are separate settings, on separate cards.
  • Integrations → Discord → Bot is who posts. It shows the bot your community sees, and Switch takes you back through setup.
  • Integrations → Discord → Server is where you post. Change servers from here.
Switch always runs the whole setup flow, whichever direction you are going: to a different bot of yours, to a brand new token, or back to the Userplay bot. That is on purpose. A bot can only post in servers it has been added to, so a new credential is a new question about the server too, and the only answer worth trusting is the one Discord gives us when you add it. The alternative is a Server card naming a server nothing can actually reach. Your channel links and announcement history are kept throughout. What changes is which bot they post under. Changing servers is the other direction and stays in its own modal: it sends you back to Discord to pick one, the same way you connected. Everything we posted in the server you leave comes down, and announcements can be posted again once the move is done.

​
Switching bots

A bot only has access to servers it has been added to, so every switch ends at the same Add the bot to your server step you connected with. You are never left holding a server that looks connected but cannot be posted to. That applies in both directions. If you set up on your own bot from the start, the Userplay bot was never in your server, so switching back to it asks you to add it. Discord also only lets a bot edit or delete its own messages. That is a rule of the platform, not a Userplay limitation, and it shapes what happens to what is already posted. Posts made by your previous bot stay in your server. Userplay can no longer edit or remove them, so anywhere one of those posts appears you will see Post again instead of an edit option. Posting again publishes a fresh message under your current bot and leaves the old one alone. This applies in both directions: moving from the Userplay bot to your own, from your own bot back to the Userplay one, and from one bot of yours to another. If you would rather not leave the old message sitting there, delete it in Discord yourself before posting again.

​
If your token stops working

Resetting a token in Discord invalidates the one we hold. When that happens, posting stops and the Discord tab shows a warning on the Bot card. Open that card and choose Switch to paste a fresh one. Your channels and your announcement history stay as they are; the flow finishes by confirming the bot is still in your server.

​
If your plan changes

Using your own bot is available on Essential and above. If your plan drops below that, Userplay deletes your stored token and moves you back to the shared Userplay bot. Your server connection stays, so the Discord tab keeps showing where you post and which bot now posts there. Because your own bot was the one you added to that server, the Userplay bot may not be in it yet. If it isn’t, the Server card shows a warning and posting stops until you add it. Open Integrations → Discord → Server → Change server and pick the same server again to finish. Your posts are not touched. They stay in your server exactly as they are, and they follow the same rule as any other bot switch: post again to bring them under the Userplay bot.