Invite the bot to your servers

Click Add Bot on the website, or Invite bot / Invite bot to server in the dashboard. Discord asks you to pick a server and approve these permissions:

• Manage Roles — assign and remove sync roles (core feature)
• Manage Nicknames — for nickname sync; revocable if you don't use it
• Change Nickname — lets CloudMod set its own nickname per server (Server Profile)
• Ban Members — network ban enforcement (a ban on your main server is applied on every sub-server)
• Kick Members · Moderate Members — the Kick and Timeout actions of Honeypot, Scam Guard and the Account Age Filter
• Manage Server — Invite Tracking (reading the invite list) and the Raid Alerts auto-lockdown
• Manage Channels — create ticket channels and temporary voice channels
• Move Members · Connect — move members into their temporary voice channel and lock or open it
• Manage Webhooks — for button-role panels (members self-assign roles) and channel mirroring
• Manage Messages — /purge, and cleaning up spam caught by the word filter, Honeypot and Scam Guard
• Attach Files — ticket transcripts, rank cards and welcome banners
• Add Reactions — suggestion voting, starboard and reaction roles
• Create Public Threads — Channel Automations (a thread per post)
• Create Instant Invite — automatic, permanent server invites for the public network profiles
• View Audit Log — shows in your logs which moderator did something, and powers Bot logs
• View Channels · Send Messages · Embed Links · Read Message History — for the log channel, auto-responses, form / application panels and live notifications
• applications.commands — for slash commands like /sync, /scan, /status

Together they cover every plugin. Invited CloudMod before these were added? Invite it again with the current link (or give the CloudMod role the missing permission in Server Settings → Roles) — /checkperms shows what's missing.

If you don't use a feature (e.g. no bans or no nickname sync), you can revoke that specific permission in Discord afterwards — everything else keeps working.

After you authorise

CloudMod takes you to a page that says CloudMod is in your server. Click Connect this server to link it to your CloudMod account. Or skip the website and run /setup in Discord (needs the Administrator permission, or being the server owner): it connects the server, switches on a few starter plugins, and lets you pick a timezone, an admin role, a welcome channel and a log channel.

Repeat the invite for every server that should participate — main server and all sub-servers.

Connected a server without inviting the bot? CloudMod can't see that server, so it can't tell what it would be changing there. If a project still lists a server the bot isn't on after 24 hours, the whole project switches to dry-run mode and all of its plugins are switched off; the project owner and the server owner get a DM with the invite link. Nothing is deleted, and nothing switches itself back on: invite the bot, then turn dry-run off and your plugins back on in the dashboard.

Mind the role hierarchy

If a role sits above CloudMod, your log shows ⛔ Role can't be assigned in orange — once per role per day, so it doesn't flood the channel. This entry is always posted, even if you switched other log categories off.

Want someone to be told? Set an admin role from your main server under Project settings → Admins & permissions (only the project owner sees this card), or with /admin setrole role:. CloudMod then pings that role when it needs a human — for a role it can't assign or a missing permission — at most once an hour. The role must be mentionable (Server Settings → Roles → Allow anyone to @mention this role), or the ping reaches nobody.