Every RestoreCord server runs on a custom Discord bot. Dashboard → Bots is where you check its health and change its credentials, presence, domain and guild access.
The bot list
Each card shows the bot's username, client ID and a live status dot — green once RestoreCord has it connected to Discord. Bots shared through sub-user access appear here too, without exposing their token or edit actions.
Aurora Gatekeeper
SharedAurora Gatekeeper • 123456789012345678
If the card says Privileged intents are disabled, Discord rejected the bot's gateway intents and it restarted without member and message-content events. Enable Server Members Intent and Message Content Intent in the Developer Portal, then restart the bot.
Credentials
Token and secret are validated against Discord as you type — a green ring means Discord accepted them. If either is regenerated in the Developer Portal, paste the new value here and save before running any server operation.
Bot Credentials
Sensitive information used to authenticate your bot
Valid Redirect URL
Invalid Redirect URL means the callback shown on this card is missing from your Discord application's OAuth2 settings. Copy it from here and add it there. With a custom domain the callback becomes that domain plus /api/callback.
Presence
Cosmetic only — this changes how the bot appears in Discord, never what it can do. Choosing Invisible hides the activity fields and clears the activity text, and updates can take up to two minutes to show.
Bot Status
Customize your bot's online presence and activity
It can take up to 2 minutes for the bot status to update. Maximum 128 characters.
Advanced settings
One card holds both the domain and the guild controls.
Advanced Settings
Additional configuration options for your bot
Domain Configuration
Customize your verification page with a custom domain
Guild Management
View and manage Discord servers your bot is currently in
Add Custom Domain opens a dialog with two tabs: a Free Domain you can activate instantly, or a Custom Domain you own and verify with a CNAME record.
Add the new callback URL in Discord before switching, and leave the old one in place until the domain is active and tested — otherwise live verification links break mid-transition.
Manage Bot Guilds lists every server the bot is installed in, so you can spot unexpected installs and leave the ones you no longer manage.
Bot Guild Management
View and manage Discord servers your bot is currently in
Aurora Community
OwnerAurora Staff
OwnerOld Test Server
Restart and delete
- Action
- Restart Bot
- Result
- Reconnects the bot to Discord. Use after credential or intent changes.
- Action
- Delete Bot
- Result
- Removes the bot and every member and server record attached to it. Servers still depending on it come back as a list to handle first.
| Action | Result |
|---|---|
| Restart Bot | Reconnects the bot to Discord. Use after credential or intent changes. |
| Delete Bot | Removes the bot and every member and server record attached to it. Servers still depending on it come back as a list to handle first. |
Deleting the wrong bot breaks verification and recovery for every server attached to it, and cannot be undone. Confirm the attached servers first.
Next steps
- Rotate credentials during a quiet period, then test verification with a staff account.
- Keep the bot role above every role it adds or removes.