Create a project

There are two ways to create a project. Both need the Administrator permission on the server, or you have to be its owner — Manage Server alone is not enough. If that isn't you, ask a server administrator or the owner to run /setup for you.

In Discord: /setup

Run /setup in your server. It connects that one server directly as a single-server project and asks for your time zone, an optional admin role, and (also optional) a welcome channel and a log channel. New members are greeted in the welcome channel, and CloudMod's log messages go to the log channel. Skip either one and set it up later with /welcome set or /logchannel set. The summary afterwards says what runs right away, what needs one more setting, and which Discord permissions are still missing.

In the dashboard

Click New project on the Your servers page, or Set it up on a server marked "CloudMod is here — not set up yet". Set it up picks that server for you and skips straight to step 2.

The wizard has four steps, the same for every project. It explains why it asks each thing, and none of the checks stops you from creating the project.

1. Main server — pick the server from the list. The bot has to be on it; those servers show "Bot is on this server". A server that is already the main server of a project is greyed out, and servers without the bot get an Invite bot button. A server that is a sub-server of a network can still get its own project, as a Single server (see Main server vs. sub-server).
2. Basics — the project name, the Language of what the bot posts for this network (it starts on your dashboard language), and Single server or Server network. A single server runs live right away; a network starts in test mode.
3. Options — the Log channel (CloudMod can create a private #cloudmod-log for you, only admins and the bot see it, or you pick an existing channel, or none), your Time zone (events, birthdays and reminders need one to mean the same time for everyone; suggested from your browser, empty means UTC) and an optional Admin role whose members can use CloudMod's admin commands in Discord.
4. Check — a summary, then two checks. The permissions check lists which of the permissions CloudMod asks for are missing on your server and what each one is needed for. The role order check shows where CloudMod's role sits in your role list, because CloudMod can only hand out roles below its own. To fix either, re-invite the bot with the full permissions or drag its role up in Server Settings → Roles; you can also create the project first and fix it later. Networks keep Start in dry-run mode on at first.

If CloudMod can't create the log channel (it needs the Manage Channels permission) or can't use the one you picked (it may be private, or CloudMod can't post there), the wizard says why and offers to pick another channel or Create without a log channel.

You land on your project's Overview, with a short checklist to get the bot working. For a network, add servers under Sub-Servers next.

The bot has to be on every server of the project. A server you connect without inviting the bot puts the whole project into dry-run mode after 24 hours, with all plugins switched off, until you invite it — see Invite the bot.

Every new project starts with Welcome, Bulk Purge and Auto-Responses switched on.