Add the bot and first steps

This page takes you from inviting the bot to a community ready to go: where to find the invite link, which permissions the bot asks for, what it does when it arrives and the list of first settings.

It is for the community owner or an administrator. Allow about ten minutes for everything.

Before you start

To add a bot to a community, Fluxer requires the Manage community permission in that community. The owner always has it.
Settings are made on the dashboard of fluxer.dispatchio.xyz: sign in with your Fluxer account (see Sign-in and account).
Your Dispatch.IO account on Fluxer is separate from the Discord one (dispatchio.xyz): settings, subscriptions and XP don't move from one platform to the other.

Inviting the bot

The website's invite buttons

Several buttons of the website open the same Fluxer authorization page:

Where	Button	Detail
Website home page (header, steps, footer)	Add to Fluxer	You pick the community on Fluxer's page.
Home page, pricing section, free plan	Add for free	You pick the community on Fluxer's page.
Dashboard, My servers list, Bot missing card	Add the bot	The community is already picked.
Page of a community without the bot	Add Dispatch.IO™	You pick the community on Fluxer's page.

The Invite the app link of the bot's introduction (when it is mentioned) and the invite link of !help also lead to a Fluxer authorization page.

My servers section of the dashboard with a Bot missing card and its Add the bot button — In My servers, the card of a community without the bot offers Add the bot: the invite opens with that community already picked.

Confirming the invite

Click one of the buttons. Fluxer's authorization page opens in a new tab.
Pick the community in the list (only those where you have Manage community appear), then continue.
Fluxer shows the requested permissions. Leave them checked (see the next section), then confirm.
The bot joins the community. On the website, the card switches to Bot active on its own; otherwise click Refresh data (see Managing communities).

Requested permissions

The invite link asks for the Administrator permission. Fluxer gives it to the role created automatically for the bot.

Keep the Administrator permission. The bot needs it for everything it does without a command: deleting the anti-raid's messages, creating ticket channels and temporary voice channels, giving welcome roles, posting logs… If you prefer a reduced list, the permissions used are detailed in Permissions and roles.

Important

Move the bot's role up

The permission is not enough: on Fluxer, a role can only give roles placed below it, and can only sanction members whose role is lower. At an equal position, the older role wins. Remember to move the bot's role up (see First steps).

What the bot does when it arrives

As soon as it joins the community, the bot goes through these steps:

The settings created on its first arrival:

Setting	Value on arrival
Community language	English: change it on the dashboard (see First steps)
Command prefix	Dispatch.IO's default prefix, `!`
Time zone	`Europe/Paris`
Color of the bot's messages	`#48D1E1`
Anti-raid whitelist	The community owner, for every protection
Level system	Off
Other modules	Off or without a channel: nothing is posted until you set them up

The bot creates no channel and no role, posts no message and sends nothing by direct message. The website dashboard detects its arrival on its own.

Note

Two cases make the bot leave right away: if the community was banned from Dispatch.IO, its owner gets a direct message with the reason; if the owner is blacklisted from Dispatch.IO, the bot leaves without a message. See the FAQ.

First steps

Here are the settings to make right after the bot arrives, on the website dashboard:

Move the bot's role up. In Community settings → Roles, drag the Dispatch.IO role above the roles it will give (welcome roles, level rewards, reaction roles) and above the members it will moderate.
Pick the language and time zone in the basic configuration: the community starts in English. The time zone splits the days of the flames.
Pick your log channels. At least the Server logs channel: every configuration change is logged there. Then add the ones you want (sanctions, messages, joins and leaves…).
Prepare the welcome: arrival channel, custom message and roles given to newcomers.
Turn on the modules you need: anti-raid, levels, flames, tickets, bump…
Change the prefix if ! is already taken by another bot: !prefix ? (see Bot configuration).
Test: !ping checks that the bot answers, !help shows the commands.

Step	On the website
Language and time zone	Community home (basic configuration)
Log channels	Logs settings
Member welcome	Welcome and goodbye
Modules	Configuration section of the menu
Staff permissions	In Fluxer: Community settings → Roles (see Permissions and roles)

Tip

No need to create channels by hand: on the dashboard's Channels page, the Create and assign button creates a ready-named text channel. Log channels created this way are hidden from @everyone.

Every option is detailed in Bot configuration.

Removing or re-inviting the bot

To remove Dispatch.IO, kick it from the community like any member.

When you remove the bot	When you re-invite it
The community's settings are kept (channels, modules, messages, members' XP…). The community switches to Bot missing on the dashboard.	You get your settings back as they were.
The aviation command pack is switched off.	Switch the aviation pack back on if you used it (page Other commands).