The dashboard

Arclo has no configuration commands. Everything is set from the dashboard, which reads and writes the same records the bot reads — there is no export step, no sync button and no restart.

The sidebar

The left column is the whole product: one row per system, 48 of them across seven groups. The dot at the end of a row says whether that system is switched on in the server you are editing.

• General — views and controls rather than systems: the Overview, Analytics, Command Info, Emojis, Logging and Settings. None of these has a master switch, because none of them is a feature you turn on.
• Onboarding & Access — what happens to somebody who arrives, and what they can earn.
• Essentials — tickets, moderation, automatic moderation, security, automations and invite tracking.
• Server Management — giveaways, custom commands, statistics channels, starboards, backups.
• Utilities — embed messages, voice tools, forms, polls, sticky messages.
• Community — boosts, birthdays, suggestions, reminders, tags.
• Social Alerts — fourteen rows over one alerts engine.

A system page

Every system page opens the same way: the system's name, a switch, and a status strip that tells you whether it can actually do its job right now.

The master switch

Off means the system does nothing at all — no listeners, no commands, no messages. Turning it off never deletes the configuration, so switching a system off to debug it and back on later is safe.

Status pills

Green means running. Amber means something is missing — usually a channel that was deleted or a permission Arclo lost. Amber problems block the system from running, never from saving: you can always finish configuring and fix the channel afterwards.

Tabs

Larger systems split into tabs — Moderation has 8, Auto Moderation 8, Security 9. Tabs are addressable: the URL carries ?tab=, so a link you paste in your staff channel opens the same tab for everyone.

Commands section

Every system page ends with the commands that system owns, where you can restrict them to roles, redirect their output or switch one off. It is the same data as the Command Info page, edited from either side.

Saving

• Most controls save as you change them; a save bar appears for the ones that batch several fields together.
• Changes reach the bot within about twenty seconds — most systems keep a short cache of their configuration so a busy server is not querying the database on every message.
• There is no publish step. If the dashboard says a message will be sent to #welcome, that is where the next arrival's message goes.

The Overview

The first page inside a server. It shows which systems are on, what needs attention, and the server's headline numbers, with a tile per system you can switch on from there.

Previews are the real thing

Wherever Arclo is going to post something — a welcome message, a ticket panel, a rank card, a boost banner — the dashboard draws it with the same code the bot uses to send it. A banner preview is rendered by the identical drawing core; a rule tester runs the identical filter. If the preview is right, the message is right.