GuardcordDocumentation
DocumentationOverview

Guardcord documentation

From your first connection to a recovery plan. Find the steps, permissions and commands you need.

Documentation overview

Set up Guardcord

Connect your Discord application, invite your bot and check its permissions.

Connect your bot

Setup checklist

Follow the setup path, or jump to the part you need.

  1. 1

    Connect a Discord bot

    Your bot, callback URL and permissions.

  2. 2

    Set up verification

    Let your members choose to authorize recovery.

  3. 3

    Save your server structure

    Capture a snapshot and review a restore.

  4. 4

    Prepare member recovery

    Check consent, connect a destination and follow progress.

Find a slash command

Examples, parameters and required access.

18 commands

Set team permissions

Choose capabilities and allowed communities.

Structure snapshots and member consent are separate. Start with the setup your community needs.

Explore resources

Connect your bot

  1. Create a Discord application

    Open the Discord Developer Portal. In the application's Bot settings, enable Server Members Intent, then copy its bot token and OAuth2 client secret.

  2. Add the callback URL

    In OAuth2 settings, add this exact URL to Redirects.

    https://stripe-test.guardcord.com/api/oauth/callback

  3. Connect and invite your bot

    Open Bots in your workspace and connect the application. Use the installation link shown there to invite it with the bot and applications.commands scopes.

  4. Check the bot's permissions

    Place its role above the verified role. It needs Manage Roles to assign roles, Manage Channels to restore structure, and permission to view and send messages in your verification channel.

Ready to use commands?

Link your own Discord account in Settings → Connect Discord. Staff commands also require Manage Server and the relevant Guardcord permissions.

Next guideSet up member verification

Member verification

  1. Choose your verification settings

    Open Servers, select your community, and enable verification. Choose a verified role, minimum account age, and optional CAPTCHA. Save your changes.

  2. Publish your verification message

    Choose a channel the bot can access. Preview your message in the workspace, or use /verify-embed in Discord and confirm the preview.

  3. Invite members to authorize recovery

    Members review the consent page and authorize through Discord. Their consent applies to this named community. They can also use /verify to check their status and open the consent page.

Every member chooses to opt in.

Existing server members are not automatically authorized. Members can remove the application's authorization in Discord at any time.

Related commands

/setup/verify/verify-embed
Next guideSave your server structure

Server backups

Create a snapshot

Use /backup or open Backups in your workspace. Daily and weekly schedules are configured per server and run while its bot is connected. You can review and download saved snapshots.

Included

Supported categories, text, voice, stage and forum channels; non-managed roles and role overwrites. Supported threads, emojis, stickers and server identity can also be captured.

Excluded

Message history and member credentials. Available assets and the bot's Discord permissions determine what can be restored.

Preview, then restore

Select a saved backup with /restore. Review the objects to create, reuse or skip, then type the destination server's Discord ID to confirm.

Restores preserve existing structure.

Guardcord adds or reuses objects by unambiguous names. It does not wipe channels or edit and reorder existing roles. Failures stay available for review.

Related commands

/backup/backups/restore
Next guideRecover consenting members

Member recovery

  1. Connect the destination

    Source and destination must use the same bot and both fall within your account's access. A disconnected original community can still be selected as the source.

  2. Restore the structure first

    Restore a snapshot to create destination roles and record source-to-destination role mappings. Keep the bot's role above every role it should assign.

  3. Review member recovery

    Use /pull in the destination server or open Recoveries. Review active authorizations and type the destination's Discord ID. Members who left the original server remain eligible until their consent or authorization is withdrawn.

  4. Track recovery progress

    Progress is saved after each member. Check /recovery status or the workspace. Use /recovery cancel to stop remaining work; completed actions stay recorded.

Recovery requires valid authorization.

Discord may refuse joins because of bans, limits, revoked access or platform enforcement. One refusal does not stop the rest of the pull.

Command referenceManage recovery from Discord

Slash commands

Replies are private. Staff commands require Manage Server and a linked Guardcord owner or team account with access to this community.

Connect your Discord account

Getting started

/helpShow commands and account setup links.Everyone

Open the command guide. Staff with a linked account also see the tools available to them.

Parameters
No parameters.
/help
/verifyCheck your consent and open verification.Everyone

Check your own recovery consent status and open this community’s consent and Discord authorization page.

Parameters
No parameters.
/verify
/setupReview or update verification settings.Staff

With no parameters, review current settings. Changes require a private confirmation. The verified role must be below the bot’s role; assigning it requires Manage Roles. Selecting a channel previews and publishes verification after confirmation. The activity-log channel stays unchanged.

Parameters
verified_role, verification_channel and enable_verification are optional.
Permissions
Manage Server + Settings access.
/setup
/statusCheck bot and community readiness.Staff

Review bot availability, verification and verified-role readiness. Backup and recovery details are shown only when your account permits them.

Parameters
No parameters.
Permissions
Manage Server + Linked owner or team access.
/status
/verify-embedPreview and publish a verification message.Staff

Review the actual message in a private preview and confirm publication. Defaults to the current channel. Title, description and button overrides affect this message only; the saved template stays unchanged. Mentions are suppressed.

Parameters
channel, title, description and button are optional.
Permissions
Manage Server + Settings access.
/verify-embed

Backups & recovery

/backupSave the current server structure.Staff

Create a snapshot immediately and receive its reference, date, role count, channel count and workspace link.

Parameters
No parameters.
Permissions
Manage Server + Backups access.
/backup
/backupsList recent server snapshots.Staff

View the five most recent snapshots for this server, including their references and workspace links.

Parameters
No parameters.
Permissions
Manage Server + Backups access.
/backups
/restorePreview and restore a saved snapshot.Staff

Select a snapshot using autocomplete. Review what will be created, reused or skipped, then type the destination server ID to confirm. Source and destination must both be within your account’s access. Restores preserve existing structure.

Parameters
backup is required. Select a saved snapshot.
Permissions
Manage Server + Backups access to source and destination.
/restore backup:<snapshot>
/pullRecover authorized members into this server.Staff

Defaults to this community as the source, or choose an authorized saved source, including a disconnected original. Review eligible members and type the destination server ID to confirm. Both communities must use the same bot.

Parameters
source is optional. Select the original community.
Permissions
Manage Server + Recovery access to source and destination.
/pull
/recoveryCheck progress or cancel remaining work.Staff

Choose a current or saved operation using autocomplete. Cancellation requests stop remaining work; completed actions remain recorded.

Parameters
status: operation is optional. cancel: operation is required.
Permissions
Manage Server + Backups access for structure restores, or Recovery access for member pulls. Access must cover source and destination.
/recovery status
/recovery cancel operation:<operation>

Members

/usercountCount recovery authorizations.Staff

See authorized and recoverable, deauthorized, and withdrawn consent counts for this community.

Parameters
No parameters.
Permissions
Manage Server + Members access.
/usercount
/infoReview a member’s verification details.Staff

View consent status, verification date, saved roles and a link to the member’s details within this community.

Parameters
user is required. Select a Discord member.
Permissions
Manage Server + Members access.
/info user:@member

Verification rules

/blacklistBlock a member from future verification.Staff

Confirm adding a member to the blocklist. This does not revoke existing consent or stop an existing recovery.

Parameters
user is required.
Permissions
Manage Server + Settings access.
/blacklist user:@member
/unblacklistRemove a verification block.Staff

Remove a member from this community’s blocklist.

Parameters
user is required.
Permissions
Manage Server + Settings access.
/unblacklist user:@member
/whitelistAdd a member to the verification allowlist.Staff

Add a member to the allowlist. This does not enable allowlist mode; a blocklist entry still takes priority.

Parameters
user is required.
Permissions
Manage Server + Settings access.
/whitelist user:@member
/unwhitelistRemove a member from the allowlist.Staff

Remove a member from this community’s verification allowlist. When allowlist mode is required, review and confirm the removal first.

Parameters
user is required.
Permissions
Manage Server + Settings access.
/unwhitelist user:@member

Cleanup

/deluserWithdraw one member’s recovery consent.Owner

Confirm withdrawing consent and clearing this community’s profile and link data. Revoked history, saved roles and credentials shared with other communities are retained. This does not kick or ban the member.

Parameters
user is required.
Permissions
Manage Server + Linked bot owner account.
/deluser user:@member
/delunauthedClean up inactive authorizations.Owner

Preview and confirm a batch of up to 500 inactive or revoked consent records. Clear scoped profile links and withdraw remaining consent while preserving history, saved roles and shared credentials. Active authorizations are excluded.

Parameters
No parameters.
Permissions
Manage Server + Linked bot owner account + your plan’s bulk capability.
/delunauthed
Commands missing in Discord?

Refresh the bot installation using its workspace invite link, then ask its owner to reconnect. Check Command registration in Bot settings and allow Discord time to show the menu. A linked account does not grant team access.

Team access

  1. Invite a registered account

    Bot owners manage access from Teams in the workspace. Choose the team member and the bot they will help manage.

  2. Choose capabilities and communities

    Grant Members, Settings, Backups or Recovery access as needed. Restrict allowed servers when the account should manage only part of your community. Recovery permissions must cover both source and destination.

  3. Link Discord for staff commands

    Each staff member links their own account through Settings → Connect Discord and needs Discord Manage Server in the server where they use commands.

Owner-only cleanup stays with the owner.

Team access does not allow /deluser or /delunauthed. Linking a Discord account does not grant workspace permissions.

Your workspaceSign in to get started