Getting started

Invite the bot

Add Cloudy to a Discord server, sign in to the dashboard and open the server you want to configure.

Getting Cloudy onto a server takes about a minute. You need to be able to manage the server — see Permissions & access for exactly what that means.

Step by step

Sign in to the dashboard

Open usecloudy.xyz and click Sign in. Authentication is Discord OAuth — there is no separate Cloudy password. Cloudy asks for two scopes:

ScopeWhy it is needed
identifyYour user id, name and avatar for the dashboard header
guildsThe list of servers you are in, so the dashboard can show which ones you may configure

Cloudy never asks for email, and it cannot read your messages through this login.

Pick a server

After signing in you land on the server selector. Every server you can manage is listed, split by state:

  • Installed — Cloudy is already a member. Click Open dashboard.
  • Setup — you can manage the server but Cloudy is not on it yet. Click Set up Cloudy.
  • No permission — you are a member but not an admin. The card is locked.

If a server you just created is missing, use the refresh button in the toolbar. The guild list is cached for a short while to stay inside Discord's rate limits.

Authorise the bot

Set up Cloudy opens Discord's authorisation screen with the target server preselected. Confirm it, and Discord adds the bot.

Keep the permissions Cloudy requests. They are the union of what the plugins need — for example Manage Roles for reaction roles and verification, Manage Channels for temp voice and channel locks, Ban Members for moderation. Stripping a permission does not break the dashboard; it makes the matching feature fail silently at runtime, which is much harder to debug later.

Open the dashboard

Back in the selector, the server now shows as installed. Open it and you land on the overview with member counts, channels, roles and server info. The sidebar on the left holds everything else.

What Cloudy does on its own

Nothing that changes your server. On join, Cloudy registers its slash commands and creates one configuration row for the server. Every plugin starts disabled, no messages are posted, no roles are touched, no channels are created.

That is deliberate: a bot that starts talking the second it joins is a bot you have to clean up after. You decide what runs.

Removing Cloudy

Kick or ban the bot from Discord like any other member. Your configuration survives — re-inviting Cloudy restores every setting exactly as it was.

To wipe the configuration as well, use Reset settings & data on the Server defaults page before removing the bot.

Next