Recovering Your Discord Account
When you lose the Discord account you sign in with: switch to your backup account in one click or prove a new one through one link, with a 24-hour undo.
Your Subscriby account is bound to one Discord account: the one you sign in with, the one your alerts reach, and the one /subscriby-admin recognises you by in your servers. When Discord disables that account, or you lose it, nothing about your projects breaks: the Subscriby app runs your servers, not your account. But you can no longer sign in with Discord, the alerts stop arriving, and the commands in your server answer that the account is not linked.
The Discord Account recovery moves that binding to a new Discord account. Nothing else changes.
First, sign in
A lost Discord account cannot use Continue with Discord, so sign in with your email and password or a passkey instead. Every creator account has all three; see If you can't sign in if you are stuck on this step. This is also why the readiness checklist asks for a second factor: the account that runs a recovery should be hard to take over.
Option 1: the one-click switch (Growth)
If you registered a backup Discord account ahead of time under Active Disaster Prevention, the recovery page shows Your backup account is ready and a single button, Switch to Backup Account. Press it and:
- sign-in with Discord, your alerts and
/subscriby-adminnow use the backup account; - the previous account is kept as your backup, so the switch can be undone the same way;
- the Discord Account allowance is spent, like any recovery.
No link, no authorisation.
Option 2: prove a new account
Without a backup, you prove the new account by signing in to it on Discord. The page names what is Currently Linked so you can see what you are moving away from.
Generate a link
Press Generate a Link. The page shows a link that works for 15 minutes. From a connected server, /subscriby-admin recovery relink gives you the same link.
Open it from the new account
Open the link in a browser where the new Discord account is signed in, and authorise Subscriby on Discord's page. The tab confirms: This Discord account (name) is ready to be linked to your Subscriby account; go back to the Disaster Recovery page and confirm the change there.
Confirm in the dashboard
The page updates on its own (it listens for the handshake) and shows Account detected: name. Press Confirm and Relink. You may be asked to confirm your password first if you have not done so in the last three hours.
Done
Sign-in with Discord, alerts and /subscriby-admin use the new account from this moment. You receive a security email with the undo link. If the new account manages your servers, give it Manage Server there, so /subscriby-admin keeps working.
What the door refuses
The handshake protects everybody's account, so the link refuses to complete when:
- it has expired (15 minutes) — generate a new one;
- the Discord account is already bound to another creator's Subscriby account — one Discord account, one creator;
- the Discord account is the one already linked — you opened the link while signed in to Discord as the old account; open it from the new one instead.
Discord's own page may also tell you the authorisation was cancelled; nothing changes then.
What changes, and what does not
| Changes | Does not change |
|---|---|
| Continue with Discord signs you in from the new account. | Email, password and passkeys. |
| Alerts reach the new account's direct messages. | Your projects, plans, subscriptions, members and payments. |
/subscriby-admin recognises the new account in your servers. | Your servers, roles and channels — the Subscriby app administers them, and it was never bound to your account. |
| The recovery history shows Linked to name. | Your members' Discord accounts and their roles. |
Undo
The security email that follows a relink carries a signed undo link, valid for 24 hours. Using it:
- puts the previous Discord account back;
- signs you out of every browser and device, so whoever is signed in has to sign in again;
- opens a relink disputed incident and tells our support team, so a relink you did not make is looked at by a person.
The undo is deliberately only in the email: a relink made by someone who took over your dashboard session cannot be defended from that same session. If you switched to a backup account instead, the same email lets you switch back.
Example: a disabled account on the day of a launch
A coach's Discord account is disabled on Friday morning, hours before their Saturday cohort opens. Their server keeps working, the app runs it, but they can no longer sign in with Discord or receive the sale alerts.
They sign in with email and password, open Disaster Recovery from the banner, and see We can no longer reach your Discord account named at the top. They had not registered a backup, so they create a new Discord account, press Generate a Link, open it signed in as the new account, authorise, and press Confirm and Relink when the dashboard shows the account. They give the new account Manage Server in their server, and /subscriby-admin recovery status answers from it a minute later.
The Discord Account allowance is now used until 90 days from Friday. A server or role problem in the meantime is unaffected; those are their own allowances.
Related
- Recovering your connected account — the connector-neutral page.
- Active Disaster Prevention — register the backup account ahead of time.
- Sign in with Discord — how the link between the two accounts works day to day.
How is this guide?
Last updated on
How the App Stays Connected
The live connection Subscriby keeps open to Discord, what runs on its own when it hiccups, and what to check when the app goes quiet in your server.
Replacing Roles and Channels
Point a place at the role or channel that takes over, re-add every member automatically, keep a standby with a live mirror of the channel's posts, and undo within 24 hours.