INSTALL / CONFIGURE / CHECK PERMISSIONS

Your first
Guardify session.

For a server administrator

Invite Guardify using an account that can manage the server.
Move Guardify’s role above the members it must moderate. Administrator permission is not required.
Run /diagnose in the channels it must protect.
Choose a restricted staff channel with /log_channel. Reports contain sensitive allegations and review details.
Inspect /dashboard, adjust filters and thresholds, and populate your custom word/domain lists.
Use /ai_settings if the operator has configured Groq. For the game, run /play.

Permission checklist

Setting	Default / behavior
Basic access	View Channel, Send Messages, Embed Links, Read Message History.
AutoMod / purge	Manage Messages.
Member moderation	Kick Members, Ban Members, Moderate Members for those respective actions.
Channel changes	Manage Channels; Manage Roles for permission overwrites used by lock/unlock.
Protected actions	Commands also check the invoking moderator’s permissions and role hierarchy.

For the bot operator

Create a separate Guardify application in the Developer Portal. Enable Message Content Intent and Server Members Intent. Set the bot token privately in .env, run setup.command, then start.command. Stop with Ctrl+C; no background service is installed.

Leave DEVELOPMENT_GUILD_ID blank for global commands. Switching command registration scope does not automatically remove old test-server commands. Command availability may take time to refresh in clients.

Discord Activity setup

In the Guardify Developer Portal, open Activities → URL Mappings.
Set prefix / to the hostname of this published site, without the https:// prefix or a path.
Enable Activities in Activities → Settings. This creates a Discord Entry Point command.
Restart the updated bot and use /play. The bot preserves the Activity Entry Point while syncing slash commands.

The solo Activity needs no OAuth2 Client Secret, bot token on the website, or AI key. Discord’s own distribution/participant settings still apply. A custom subdomain can be connected later; only then update URL Mappings to the new hostname.

Troubleshooting

Bot offline or commands absent?

Keep its Terminal running, check startup errors and token, verify intents, and check the bot was installed with bot and applications.commands scopes.

AI unavailable?

The owner should check the key, model access, provider quota and local daily limit. AutoMod and the fixed-content game do not need AI.

Activity will not open?