Adding Arclo

Invite the bot, give it the permissions it needs, put its role in the right place, and confirm it is working — in about two minutes.

On this page

You need Manage Server in the server you are adding Arclo to. Discord only shows servers you hold that permission in on the invite screen.

Invite the bot

  1. Open the invite link

    Use the Add to Discord button anywhere on this site, or go straight to the invite page.

  2. Pick the server

    Choose it from the dropdown. If the server is not listed, you do not have Manage Server there — ask an admin to add Arclo, or to give you the permission.

  3. Leave the permissions ticked

    The invite asks for Administrator and, alongside it, every individual permission Arclo uses. That is deliberate: Administrator means nothing can fail later over a box somebody forgot, and the individual grants mean you can untick Administrator — on this screen, or on Arclo's role at any point afterwards — and still have a fully working bot rather than one that does nothing. If you would rather grant less than that, trim Arclo's role in Server Settings → Roles after authorising: Permissions Arclo needs lists exactly what each system uses and what stops working without it.

  4. Authorise

    Arclo joins immediately and appears in your member list. It does nothing else until you switch a system on.

Nothing happens yet — that is deliberate

A freshly added Arclo does not moderate, log, greet, level or announce anything. Every system starts switched off, so adding the bot to try tickets cannot quietly start deleting messages.

Move Arclo's role up

This is the single most common cause of “the bot is not working”, and it takes ten seconds to fix.

Discord will not let any bot act on a member whose highest role is above the bot's own. Arclo cannot ban, mute, kick, or add a role to somebody who outranks it, and it cannot hand out a role that sits above its own role in the list.

  1. Open Server Settings → Roles

    Find the role Discord created when Arclo joined — it is called Arclo and is managed by the integration.

  2. Drag it above the roles it has to manage

    As a rule: above every member and moderator role, below your owner/admin roles. It does not need to be at the very top.

Roles Arclo cannot reach are invisible to it

Role pickers in the dashboard mark anything above Arclo's role, and the Settings page shows a warning banner when Arclo has no Manage Roles at all. If a reward role never lands, check the ladder first.

Open the dashboard

  1. Log in with Discord

    Click Log in in the top-right of this site. Arclo asks Discord for your identity and your server list, nothing else.

  2. Pick your server

    The picker lists every server you own or hold Administrator in, plus any where you were given dashboard access explicitly — a Bot Master role or a per-page grant. Manage Server on its own is not enough. Servers without Arclo show an Add Arclo button instead of Manage.

Choose a server

Servers where you hold Manage Server — plus any where a role you have was granted dashboard access.

NC

Nebula Collective

12,480 members

Manage
PF

Pixel Foundry

3,102 members

Manage
TL

The Lounge

854 members

Add Arclo
The server picker, immediately after logging in.

Check it is alive

Type /about in any channel Arclo can see. You should get a reply with the bot's version, uptime and links. If the command does not appear in the slash menu at all, Discord has not finished syncing the command list — give it a minute, then reload Discord with Ctrl + R.

Then go set something up

Your first 15 minutes walks through the five systems most servers want on day one.

Removing Arclo

Kick the bot like any member. Its commands disappear from your server within a minute or two.

Removing Arclo deletes your configuration after 14 days

When Arclo is removed from a server, that server's stored settings and data — every system's configuration, levels, cases, tickets and counters — are marked for deletion and removed permanently 14 days later. Re-add the bot inside those 14 days and everything comes back exactly as it was. After that it is gone and cannot be recovered. Backups and templates are stored outside the cascade on purpose and survive either way. If you are only troubleshooting, you still do not need to kick the bot: switch the system off instead.

Still stuck? Ask in the support server — somebody there has almost certainly configured this before.