A Discord backup bot with a recovery plan.

Protect the layout and the people separately

A structure snapshot saves supported roles, categories and channels so your team can rebuild the places where your community talks. Member recovery uses a different record: a member's active consent and valid Discord authorization for the original community. A list of user IDs or a downloaded snapshot does not grant permission to add people to another server.

Keeping these two parts separate makes your recovery plan easier to evaluate. Check your snapshot coverage and your active member authorizations before an incident, rather than assuming the server's total member count is recoverable.

From your first snapshot to a reviewed restore

Structure restores add missing objects or reuse unambiguous matches. They preserve existing destination content. Channels with member-specific permission overwrites need manual review and are skipped, along with children of a skipped category.

• Connect an application you own and invite the bot to the servers you manage.
• Publish a verification message so members can review and grant community recovery consent.
• Create a structure snapshot on demand or set a daily or weekly schedule.
• Select a connected destination and inspect the restore preview.
• Restore supported structure, then run a separate recovery for eligible members.
• Review the job logs for completed, skipped and failed actions.

Give your team the access it needs

Owners can grant teammates specific permissions and restrict access to selected servers. That matters when one team manages several communities: the ability to view members should not automatically authorize a restore anywhere. Use the dashboard's protection checklist, member records and activity history to review your setup before handing off an incident.

Know the limits before you need the backup

Structure snapshots exclude message history, files, member credentials and integration-managed objects. Optional read-only message archives are a separate feature; they do not recreate conversations in Discord. Member joins can fail because authorization was revoked, the member is banned, a Discord limit was reached or required bot permissions are missing. Guardcord cannot guarantee every member will return.