Member backup & recovery
Discord member recovery starts with permission.
A Discord member backup is useful only when members have authorized a recovery attempt. Guardcord records permission for a named community, keeps recovery credentials encrypted and lets members withdraw consent. Owners can review eligible records before moving to a connected destination.
Recover members to a connected destination
When you need to move, choose the source community and a connected destination you have permission to manage. A recovery job attempts joins only for eligible authorizations. Saved non-managed member roles can be applied when the destination has a mapped or uniquely named match.
The dashboard records progress and individual outcomes. Jobs save their position so progress can resume after a restart, and owners can request cancellation. A Discord request already in flight can still complete after cancellation; a completed join is not reversed automatically.
Why a verified member might not return
Active consent is necessary but does not guarantee a successful join. Discord can refuse a request because the member revoked application access, is banned from the destination, reached a server limit or is affected by platform enforcement. Missing bot permissions can also prevent recovery or role assignment.
Use the logs to distinguish skipped authorization from a failed join. Review the specific cause before retrying. An account that withdrew permission should not be treated as a recovery error to work around.
Let members control their community permission
Leaving the source server does not withdraw recovery consent. Members can use Privacy & consent to withdraw from a community or remove the application under Discord's Authorized Apps. Withdrawing the final active community consent deletes stored authorization credentials and member profile data; minimal revoked consent records remain to prevent accidental recovery.
Switching backup services is a separate setup decision. Guardcord has no cross-provider member token import. Plan for members to authorize the application connected to Guardcord rather than assuming another provider's export grants access.
Common questions
Can I pull all members from a Discord server?
Guardcord can attempt recovery only for members with active community consent and valid authorization. Unverified members, revoked consent and Discord refusals prevent a complete member pull.
Can I restore members after a server is deleted?
Prior eligible authorization can support a recovery attempt to a connected replacement server. Guardcord cannot recreate an uncaptured member authorization or reverse a Discord enforcement decision.
Can members opt out after verifying?
Yes. Members can withdraw community consent through Guardcord or revoke application access in Discord. Leaving the community alone does not withdraw the recorded consent.
Prepare while your community is healthy.
Connect your application, review your coverage and keep a way back.