Your community's recovery plan

1. Create your application in the Discord Developer Portal .

   In Bot settings, enable Server Members Intent. Copy the bot token and OAuth2 client secret.

2. Add the OAuth2 redirect URL.
   https://guardcord.com/api/oauth/callback

   The URL must exactly match your hosted Guardcord origin.

3. Open Bots in your dashboard and connect the application.

   Guardcord validates the token before saving encrypted credentials. Use its invite link to add the bot to your community.

4. Check permissions.

   Keep the bot role above any verification role it assigns. It needs Manage Roles for role assignment, Manage Channels for structure restores, and access to the channel where you publish verification.

Open Servers, select your community and enable verification. Choose an optional verified role, account-age requirement and CAPTCHA. Save, then publish a verification message to a channel the bot can access.

Members review the consent page before Discord authorization. The member list shows active and deauthorized records. Members can manage consent from Privacy & consent or revoke the application in Discord.

Use Backups to create and review snapshots. Schedules are configured per server and run while its bot is connected. Download a copy whenever you need it.

Snapshots cover supported category, text and voice channels, non-managed roles and role overwrites. They exclude messages, files, threads, forums and emojis. Newly created roles are ordered when the destination has no matching role names. Existing roles are not edited or reordered.

Restoring adds or reuses objects by unambiguous names. It preserves existing objects and records failures for your review.

1. Connect the destination server to the same bot.

   The destination must belong to the permissions granted to your account.

2. Restore structure before pulling members into a new server.

   That creates the destination roles and records how source roles map to them. Keep the bot role above every role it should assign.

3. Choose the original community and destination in Recoveries.

   Review the active consent count and confirm the destination's Discord ID. Members who left are still included until they withdraw consent.

4. Follow the operation log.

   Joins require valid authorization. Discord may refuse them because of bans, limits, revoked access or platform enforcement. One refusal does not stop the rest of the pull. You can request cancellation of remaining work.

5. Leave a restart running.

   Progress is saved after each member. A Coolify restart continues the same recovery when the bot reconnects. A cancellation requested before the restart is kept.

Working with your team

Bot owners can invite registered accounts from Teams, choose their permissions and restrict allowed servers. Recovery permissions cover both source and destination.