Complete guide

UltimateBot documentation

A clear path for new users and staff teams: install the bot, set up security and get every module running in no time.

Add the bot Support server See modules

Last reviewed: 2026-04-24 · Public guide

Guided start
A step-by-step path to get the bot running.
15 modules explained
Goals, usage and real examples for each area.
Best practices
For small and large servers.

Quick start from scratch

Follow this order to switch on what matters without wasting time.

1
Add the bot
The link only asks for the permissions the bot uses. Move its role above the roles it has to manage.
2
Set up basic security
Turn on anti-spam, anti-raid and verification before opening the server to the public.
3
Prepare moderation
Define the warning and punishment flow so all staff follow the same criteria.
4
Turn on support and automations
Set up tickets and automatic responses to cut your team’s manual work.
5
Create your first backup
Save a stable version of the server so you can roll back in minutes.

Setting up the dashboard properly

The recommended path to get UltimateBot running from the web dashboard.

1Access and active server

The top selector shows the right server and the bot shows as online.

2General settings

Open Server › General settings to set the prefix, language, maintenance mode and main log channel.

The chosen channel exists, the bot can write in it and the prefix doesn’t clash with other bots.

3Security and moderation

Set up anti-raid, anti-spam, anti-links, verification, authorised roles, admin roles, warn escalation and automatic punishments.

Start with conservative thresholds and review the events in Logs before making punishments stricter.

4Modules and role permissions

Go to Modules to turn on what the server will use and to Roles and permissions to limit dashboard actions and commands by role.

Keep staff, moderator, administrator and owner permissions separate.

5Plan and Premium

With Premium, open Plan and Premium to see the included features and turn each one on or off: Tickets Pro, backup protection, advanced auto-moderation, music and more.

A Premium section doesn’t load data if its switch is off, even if the server has Premium.

6Staff team

Open Moderation and security › Staff team, create levels, map Discord roles and then assign your staff members.

Save the hierarchy before assigning members; assignments are kept and reloaded when you open the dashboard.

7Tickets, backups and tests

Set up ticket panels, transcripts, staff role, category, per-user limits and backups. Post a test panel and create a base backup.

Open and close a real ticket, check the transcript and make sure the backup shows up in the list.

8Final review

Go through Overview, Logs, Sanctions, Ticket inbox and Statistics. Fix channels without permissions and write down who can change each section.

After restarting the dashboard, reopen the key sections and confirm they keep their data.

Command reference

Every slash command in one place. Filter by name, module or description. See the full command directory

Command	Module	What it does
`/config log_channel`	Settings	Sets the log channel.
`/config anti_raid`	Settings	Sets up raid detection.
`/config anti_spam`	Settings	Sets up anti-spam.
`/config anti_links`	Settings	Per-channel link control.
`/config verification`	Settings	Sets up verification.
`/config welcome/config goodbye`	Settings	Welcome/goodbye messages.
`/config warn_escalation`	Settings	Automatic escalation by warns.
`/config backup/config restore`	Settings Premium	Settings backup.
`/config status`	Settings	Current settings status.
`/ban/unban/kick`	Moderation	Main punishments.
`/mute/unmute`	Moderation	Temporary timeout.
`/warn/warnings/delwarn`	Moderation	Warning management.
`/modhistory`	Moderation	Moderation history.
`/purge/slowmode`	Moderation	Chat control.
`/massban/unbanall`	Moderation	Mass actions.
`/panel`	Moderation	Interactive moderation panel.
`/config anti_raid`	Auto-mod	Anti-raid for mass joins.
`/config anti_spam`	Auto-mod	Automatic anti-spam.
`/config anti_links`	Auto-mod	Link filtering.
`/config anti_nuke_threshold/config punishment`	Auto-mod	Anti-nuke threshold and punishment.
`/readonly/readonly_off`	Auto-mod	Emergency read-only mode.
`/badwords_add/badwords_remove/badwords_list`	Auto-mod	Banned words.
`/config log_channel`	Logs	Main log channel.
`/config invite_log`	Logs	Invite log.
`/auditlog`	Logs	Admin activity.
`/whois`	Logs	Detailed user info.
`/config welcome`	Welcome/Leave	Welcome message.
`/config goodbye`	Welcome/Leave	Goodbye message.
`/config verification`	Welcome/Leave	Entry control.
`/rank`	Levels Premium	User level.
`/leaderboard`	Levels Premium	Level leaderboard.
`/rewards`	Levels Premium	Level rewards.
`/ticket close/ticket claim`	Tickets Premium	Actions on the current ticket.
`/ticket add/ticket addrole`	Tickets Premium	Add a user or role to the ticket.
`/ticket note/ticket rename`	Tickets Premium	Internal notes and renaming.
`/ticket list/tickets info`	Tickets Premium	Ticket list and metrics.
`/ticket panel create/list/edit/delete/publish`	Tickets Premium	Ticket panel management.
`/emoji_backup`	Emoji	Exports emojis to a ZIP.
`/emoji_restore`	Emoji Premium	Restores emojis from a ZIP.
`/premium_status/premium_sync`	Premium Premium	Premium status and sync.
`/premium_features/premium_feature_toggle`	Premium Premium	View/enable Premium features.
`/premium_analytics`	Premium Premium	Premium analytics summary.
`/integration_status`	Premium Premium	External integrations status.
`/set_backup_limit`	Premium Premium	Maximum backup limit.
Sin slash commands en este build	Economy Premium	Managed from the dashboard (Modules).
`/giveaway`	Giveaways Premium	Creates a basic reaction giveaway.
`/autoresponse_add/remove/list`	Automation	Automatic responses.
`/custom_command_add/remove/list`	Automation	Custom commands.
`/event_create/list/join/remind`	Automation	Server events.
`/autoreact_add/remove/list`	Automation Premium	Automatic reactions.
`/rolesync`	Automation Premium	Role sync.
`/schedule_message`	Automation Premium	Scheduled messages.
`/birthday_set/remove`	Automation Premium	Birthday management.
`/autorole_time_add/remove/list`	Automation Premium	Time-based autoroles.
`/announce/embed_builder`	Automation Premium	Announcements and embed builder.
`/lockdown/unlock`	Security	Emergency lock and unlock.
`/readonly/readonly_off`	Security	Temporary read-only.
`/report`	Security	Reports to staff.
`/permissions`	Security	Effective user permissions.
`/badwords_add/remove/list`	Security	Banned word management.
`/test_antinuke`	Security	Anti-nuke alert test.
`/temprole`	Security Premium	Assigns a temporary role.
`/antinuke_whitelist_add/remove/list`	Security Premium	Anti-nuke whitelist.
`/invite`	Utilities	Safe invite.
`/remind/remind_list/remind_cancel`	Utilities	Personal reminders.
`/poll`	Utilities	Timed poll.
`/giveaway`	Utilities	Basic giveaway.
`/roleinfo/channelinfo/serverinfo`	Utilities	Server information.
`/ping/uptime`	Utilities	Bot status.
`/activity_dashboard/growth_chart`	Utilities	Activity analytics.
`/avatar/banner`	Utilities	Media lookup.
`/temp/temp_list/temp_cancel`	Utilities Premium	Temporary messages.
`/rank/leaderboard/rewards`	Utilities Premium	Level system.
`/backup create/backup list/backup info/backup delete`	Backups	Core backup cycle.
`/backup restore/backup schedule`	Backups	Restore and scheduling.
`/backup compare/backup export`	Backups Premium	Compare and export backups.

Complete guide by module

Each module includes a quick setup, what it lets you do, commands and practical examples.

Settings

Free + Premium

Top

The Settings module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations.

Quick setup

Free part

Open the dashboard and go to the Settings module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Settings configuration and save the changes.

Premium part

Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Free part

Centralise Settings with less manual work.
Cut staff response times.
Standardise the server’s operating rules.

Premium part

Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Free

/config log_channel

Sets the log channel.

#staff-logs.
/config anti_raid

Sets up raid detection.

threshold 10 in 10s.
/config anti_spam

Sets up anti-spam.

5 messages in 5s.
/config anti_links

Per-channel link control.

domain whitelist.
/config verification

Sets up verification.

emoji mode and verified role.
/config welcome/config goodbye

Welcome/goodbye messages.

text with {user}.
/config warn_escalation

Automatic escalation by warns.

warn 3 => mute.
/config status

Current settings status.

review active settings.

Premium

/config backup/config restore

Settings backup.

restore previous settings.

Dashboard configuration examples6

Profile 1: Small community

Goal: make Settings stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Settings. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 2: Medium community

Goal: make Settings stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Settings. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 3: Large community

Goal: make Settings stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Settings. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 4: Support server

Goal: make Settings stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Settings. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 5: Gaming server

Goal: make Settings stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Settings. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 6: Education server

Goal: make Settings stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Settings. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Usage guides3

Daily use

Scenario: normal Settings operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Settings.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Settings module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Settings configuration.
Start of day: check the permissions needed to run Settings.
On shift: use only documented Settings commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices6

Assign one main Settings owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.

Visual examples0

This module doesn’t have example images yet.

Moderation

Free

Top

The Moderation module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations.

Quick setup

Free part

Open the dashboard and go to the Moderation module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Moderation configuration and save the changes.
Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Free part

Centralise Moderation with less manual work.
Cut staff response times.
Standardise the server’s operating rules.
Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Free

/ban/unban/kick

Main punishments.

ban for a serious offence.
/mute/unmute

Temporary timeout.

mute for 30 minutes.
/warn/warnings/delwarn

Warning management.

remove a wrong warn.
/modhistory

Moderation history.

review repeat offences.
/purge/slowmode

Chat control.

enable slowmode at peaks.
/massban/unbanall

Mass actions.

clean a raid by IDs.
/panel

Interactive moderation panel.

open quick tools.

Dashboard configuration examples6

Profile 1: Small community

Goal: make Moderation stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Moderation. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 2: Medium community

Goal: make Moderation stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Moderation. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 3: Large community

Goal: make Moderation stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Moderation. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 4: Support server

Goal: make Moderation stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Moderation. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 5: Gaming server

Goal: make Moderation stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Moderation. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 6: Education server

Goal: make Moderation stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Moderation. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Usage guides3

Daily use

Scenario: normal Moderation operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Moderation.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Moderation module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Moderation configuration.
Start of day: check the permissions needed to run Moderation.
On shift: use only documented Moderation commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices6

Assign one main Moderation owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.

Visual examples0

This module doesn’t have example images yet.

Auto-mod

Free

Top

The Auto-mod module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations.

Quick setup

Free part

Open the dashboard and go to the Auto-mod module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Auto-mod configuration and save the changes.
Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Free part

Centralise Auto-mod with less manual work.
Cut staff response times.
Standardise the server’s operating rules.
Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Free

/config anti_raid

Anti-raid for mass joins.

threshold 10/10s.
/config anti_spam

Automatic anti-spam.

10 min timeout.
/config anti_links

Link filtering.

domain whitelist.
/config anti_nuke_threshold/config punishment

Anti-nuke threshold and punishment.

alert on critical actions.
/readonly/readonly_off

Emergency read-only mode.

temporary lock during an attack.
/badwords_add/badwords_remove/badwords_list

Banned words.

block recurring insults.

Dashboard configuration examples6

Profile 1: Small community

Goal: make Auto-mod stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Auto-mod. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 2: Medium community

Goal: make Auto-mod stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Auto-mod. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 3: Large community

Goal: make Auto-mod stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Auto-mod. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 4: Support server

Goal: make Auto-mod stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Auto-mod. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 5: Gaming server

Goal: make Auto-mod stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Auto-mod. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 6: Education server

Goal: make Auto-mod stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Auto-mod. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Usage guides3

Daily use

Scenario: normal Auto-mod operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Auto-mod.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Auto-mod module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Auto-mod configuration.
Start of day: check the permissions needed to run Auto-mod.
On shift: use only documented Auto-mod commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices6

Assign one main Auto-mod owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.

Visual examples0

This module doesn’t have example images yet.

Logs

Free

Top

The Logs module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations.

Quick setup

Free part

Open the dashboard and go to the Logs module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Logs configuration and save the changes.
Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Free part

Centralise Logs with less manual work.
Cut staff response times.
Standardise the server’s operating rules.
Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Free

/config log_channel

Main log channel.

#staff-logs.
/config invite_log

Invite log.

invite monitor.
/auditlog

Admin activity.

recent changes.
/whois

Detailed user info.

check account age and roles.

Dashboard configuration examples6

Profile 1: Small community

Goal: make Logs stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Logs. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 2: Medium community

Goal: make Logs stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Logs. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 3: Large community

Goal: make Logs stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Logs. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 4: Support server

Goal: make Logs stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Logs. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 5: Gaming server

Goal: make Logs stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Logs. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 6: Education server

Goal: make Logs stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Logs. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Usage guides3

Daily use

Scenario: normal Logs operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Logs.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Logs module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Logs configuration.
Start of day: check the permissions needed to run Logs.
On shift: use only documented Logs commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices6

Assign one main Logs owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.

Visual examples0

This module doesn’t have example images yet.

Welcome/Leave

Free

Top

The Welcome/Leave module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations.

Quick setup

Free part

Open the dashboard and go to the Welcome/Leave module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Welcome/Leave configuration and save the changes.
Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Free part

Centralise Welcome/Leave with less manual work.
Cut staff response times.
Standardise the server’s operating rules.
Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Free

/config welcome

Welcome message.

welcome with placeholders.
/config goodbye

Goodbye message.

goodbye in a staff channel.
/config verification

Entry control.

role after captcha.

Dashboard configuration examples6

Profile 1: Small community

Goal: make Welcome/Leave stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Welcome/Leave. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 2: Medium community

Goal: make Welcome/Leave stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Welcome/Leave. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 3: Large community

Goal: make Welcome/Leave stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Welcome/Leave. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 4: Support server

Goal: make Welcome/Leave stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Welcome/Leave. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 5: Gaming server

Goal: make Welcome/Leave stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Welcome/Leave. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 6: Education server

Goal: make Welcome/Leave stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Welcome/Leave. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Usage guides3

Daily use

Scenario: normal Welcome/Leave operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Welcome/Leave.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Welcome/Leave module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Welcome/Leave configuration.
Start of day: check the permissions needed to run Welcome/Leave.
On shift: use only documented Welcome/Leave commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices6

Assign one main Welcome/Leave owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.

Visual examples0

This module doesn’t have example images yet.

Levels

Premium

Top

The Levels module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations. It includes the Premium options, shown in this guide.

Quick setup

Premium part

Open the dashboard and go to the Levels module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Levels configuration and save the changes.
Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Premium part

Centralise Levels with less manual work.
Cut staff response times.
Standardise the server’s operating rules.
Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Premium

/rank

User level.

/rank @user.
/leaderboard

Level leaderboard.

server top 10.
/rewards

Level rewards.

see roles per level.

Dashboard configuration examples7

Profile 1: Small community

Goal: make Levels stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Levels. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 2: Medium community

Goal: make Levels stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Levels. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 3: Large community

Goal: make Levels stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Levels. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 4: Support server

Goal: make Levels stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Levels. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 5: Gaming server

Goal: make Levels stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Levels. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 6: Education server

Goal: make Levels stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Levels. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Intensive Premium profile

Goal: use every Premium option of Levels.

How to set it up: Dashboard path: Modules > Levels > Premium settings. Enable the advanced features, save, test high-demand scenarios and confirm in the logs.
Suggested values: proactive alerts, live dashboards and automations supervised by staff.
Note: Premium features are marked with a badge, but the whole documentation is visible to everyone.

Usage guides3

Daily use

Scenario: normal Levels operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Levels.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Levels module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Levels configuration.
Start of day: check the permissions needed to run Levels.
On shift: use only documented Levels commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices7

Assign one main Levels owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.
Premium badges mark the advanced Levels features; they stay visible to everyone in the guide.

Visual examples0

This module doesn’t have example images yet.

Tickets

Premium

Top

The Tickets module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations. It includes the Premium options, shown in this guide.

Quick setup

Premium part

Open the dashboard and go to the Tickets module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Tickets configuration and save the changes.
Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Premium part

Centralise Tickets with less manual work.
Cut staff response times.
Standardise the server’s operating rules.
Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Premium

/ticket close/ticket claim

Actions on the current ticket.

staff claim.
/ticket add/ticket addrole

Add a user or role to the ticket.

add a supervisor.
/ticket note/ticket rename

Internal notes and renaming.

follow-up note.
/ticket list/tickets info

Ticket list and metrics.

review support workload.
/ticket panel create/list/edit/delete/publish

Ticket panel management.

post a panel in #support.

Dashboard configuration examples7

Profile 1: Small community

Goal: make Tickets stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Tickets. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 2: Medium community

Goal: make Tickets stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Tickets. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 3: Large community

Goal: make Tickets stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Tickets. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 4: Support server

Goal: make Tickets stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Tickets. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 5: Gaming server

Goal: make Tickets stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Tickets. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 6: Education server

Goal: make Tickets stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Tickets. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Intensive Premium profile

Goal: use every Premium option of Tickets.

How to set it up: Dashboard path: Modules > Tickets > Premium settings. Enable the advanced features, save, test high-demand scenarios and confirm in the logs.
Suggested values: proactive alerts, live dashboards and automations supervised by staff.
Note: Premium features are marked with a badge, but the whole documentation is visible to everyone.

Usage guides3

Daily use

Scenario: normal Tickets operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Tickets.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Tickets module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Tickets configuration.
Start of day: check the permissions needed to run Tickets.
On shift: use only documented Tickets commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices7

Assign one main Tickets owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.
Premium badges mark the advanced Tickets features; they stay visible to everyone in the guide.

Visual examples0

This module doesn’t have example images yet.

Emoji

Free + Premium

Top

The Emoji module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations.

Quick setup

Free part

Open the dashboard and go to the Emoji module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Emoji configuration and save the changes.

Premium part

Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Free part

Centralise Emoji with less manual work.
Cut staff response times.
Standardise the server’s operating rules.

Premium part

Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Free

/emoji_backup

Exports emojis to a ZIP.

monthly backup.

Premium

/emoji_restore

Restores emojis from a ZIP.

recover an emoji pack.

Dashboard configuration examples6

Profile 1: Small community

Goal: make Emoji stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Emoji. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 2: Medium community

Goal: make Emoji stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Emoji. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 3: Large community

Goal: make Emoji stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Emoji. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 4: Support server

Goal: make Emoji stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Emoji. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 5: Gaming server

Goal: make Emoji stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Emoji. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 6: Education server

Goal: make Emoji stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Emoji. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Usage guides3

Daily use

Scenario: normal Emoji operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Emoji.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Emoji module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Emoji configuration.
Start of day: check the permissions needed to run Emoji.
On shift: use only documented Emoji commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices6

Assign one main Emoji owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.

Visual examples0

This module doesn’t have example images yet.

Premium

Top

The Premium module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations.

Quick setup

Premium part

Open the dashboard and go to the Premium module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Premium configuration and save the changes.
Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Premium part

Centralise Premium with less manual work.
Cut staff response times.
Standardise the server’s operating rules.
Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Premium

/premium_status/premium_sync

Premium status and sync.

sync after purchase.
/premium_features/premium_feature_toggle

View/enable Premium features.

enable tickets_advanced.
/premium_analytics

Premium analytics summary.

advanced metrics.
/integration_status

External integrations status.

check API keys.
/set_backup_limit

Maximum backup limit.

raise the limit to 100.

Dashboard configuration examples6

Profile 1: Small community

Goal: make Premium stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Premium. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 2: Medium community

Goal: make Premium stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Premium. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 3: Large community

Goal: make Premium stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Premium. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 4: Support server

Goal: make Premium stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Premium. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 5: Gaming server

Goal: make Premium stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Premium. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 6: Education server

Goal: make Premium stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Premium. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Usage guides3

Daily use

Scenario: normal Premium operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Premium.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Premium module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Premium configuration.
Start of day: check the permissions needed to run Premium.
On shift: use only documented Premium commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices6

Assign one main Premium owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.

Visual examples0

This module doesn’t have example images yet.

Economy

Premium

Top

The Economy module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations. It includes the Premium options, shown in this guide.

Quick setup

Premium part

Open the dashboard and go to the Economy module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Economy configuration and save the changes.
Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Premium part

Centralise Economy with less manual work.
Cut staff response times.
Standardise the server’s operating rules.
Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Premium

Sin slash commands en este build

Managed from the dashboard (Modules).

turn on/off in the dashboard.

Dashboard configuration examples7

Profile 1: Small community

Goal: make Economy stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Economy. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 2: Medium community

Goal: make Economy stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Economy. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 3: Large community

Goal: make Economy stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Economy. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 4: Support server

Goal: make Economy stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Economy. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 5: Gaming server

Goal: make Economy stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Economy. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 6: Education server

Goal: make Economy stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Economy. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Intensive Premium profile

Goal: use every Premium option of Economy.

How to set it up: Dashboard path: Modules > Economy > Premium settings. Enable the advanced features, save, test high-demand scenarios and confirm in the logs.
Suggested values: proactive alerts, live dashboards and automations supervised by staff.
Note: Premium features are marked with a badge, but the whole documentation is visible to everyone.

Usage guides3

Daily use

Scenario: normal Economy operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Economy.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Economy module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Economy configuration.
Start of day: check the permissions needed to run Economy.
On shift: use only documented Economy commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices7

Assign one main Economy owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.
Premium badges mark the advanced Economy features; they stay visible to everyone in the guide.

Visual examples0

This module doesn’t have example images yet.

Giveaways

Premium

Top

The Giveaways module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations. It includes the Premium options, shown in this guide.

Quick setup

Premium part

Open the dashboard and go to the Giveaways module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Giveaways configuration and save the changes.
Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Premium part

Centralise Giveaways with less manual work.
Cut staff response times.
Standardise the server’s operating rules.
Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Premium

/giveaway

Creates a basic reaction giveaway.

special role giveaway for 24h.

Dashboard configuration examples7

Profile 1: Small community

Goal: make Giveaways stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Giveaways. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 2: Medium community

Goal: make Giveaways stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Giveaways. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 3: Large community

Goal: make Giveaways stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Giveaways. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 4: Support server

Goal: make Giveaways stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Giveaways. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 5: Gaming server

Goal: make Giveaways stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Giveaways. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 6: Education server

Goal: make Giveaways stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Giveaways. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Intensive Premium profile

Goal: use every Premium option of Giveaways.

How to set it up: Dashboard path: Modules > Giveaways > Premium settings. Enable the advanced features, save, test high-demand scenarios and confirm in the logs.
Suggested values: proactive alerts, live dashboards and automations supervised by staff.
Note: Premium features are marked with a badge, but the whole documentation is visible to everyone.

Usage guides3

Daily use

Scenario: normal Giveaways operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Giveaways.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Giveaways module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Giveaways configuration.
Start of day: check the permissions needed to run Giveaways.
On shift: use only documented Giveaways commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices7

Assign one main Giveaways owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.
Premium badges mark the advanced Giveaways features; they stay visible to everyone in the guide.

Visual examples0

This module doesn’t have example images yet.

Automation

Free + Premium

Top

The Automation module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations.

Quick setup

Free part

Open the dashboard and go to the Automation module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Automation configuration and save the changes.

Premium part

Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Free part

Centralise Automation with less manual work.
Cut staff response times.
Standardise the server’s operating rules.

Premium part

Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Free

/autoresponse_add/remove/list

Automatic responses.

rules FAQ.
/custom_command_add/remove/list

Custom commands.

/support with instructions.
/event_create/list/join/remind

Server events.

weekly event with reminder.

Premium

/autoreact_add/remove/list

Automatic reactions.

reaction on announcements.
/rolesync

Role sync.

copy mirrored roles.
/schedule_message

Scheduled messages.

daily announcement.
/birthday_set/remove

Birthday management.

set your personal date.
/autorole_time_add/remove/list

Time-based autoroles.

role after 30 days.
/announce/embed_builder

Announcements and embed builder.

formatted announcement.

Dashboard configuration examples6

Profile 1: Small community

Goal: make Automation stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Automation. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 2: Medium community

Goal: make Automation stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Automation. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 3: Large community

Goal: make Automation stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Automation. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 4: Support server

Goal: make Automation stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Automation. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 5: Gaming server

Goal: make Automation stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Automation. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 6: Education server

Goal: make Automation stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Automation. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Usage guides3

Daily use

Scenario: normal Automation operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Automation.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Automation module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Automation configuration.
Start of day: check the permissions needed to run Automation.
On shift: use only documented Automation commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices6

Assign one main Automation owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.

Visual examples0

This module doesn’t have example images yet.

Security

Free + Premium

Top

The Security module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations.

Quick setup

Free part

Open the dashboard and go to the Security module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Security configuration and save the changes.

Premium part

Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Free part

Centralise Security with less manual work.
Cut staff response times.
Standardise the server’s operating rules.

Premium part

Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Free

/lockdown/unlock

Emergency lock and unlock.

lock during a raid.
/readonly/readonly_off

Temporary read-only.

freeze chat during an incident.
/report

Reports to staff.

report a user with evidence.
/permissions

Effective user permissions.

debug access in the current channel.
/badwords_add/remove/list

Banned word management.

add a blocked word.
/test_antinuke

Anti-nuke alert test.

validate the settings.

Premium

/temprole

Assigns a temporary role.

24h temporary role.
/antinuke_whitelist_add/remove/list

Anti-nuke whitelist.

exclude trusted bots.

Dashboard configuration examples6

Profile 1: Small community

Goal: make Security stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Security. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 2: Medium community

Goal: make Security stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Security. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 3: Large community

Goal: make Security stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Security. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 4: Support server

Goal: make Security stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Security. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 5: Gaming server

Goal: make Security stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Security. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 6: Education server

Goal: make Security stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Security. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Usage guides3

Daily use

Scenario: normal Security operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Security.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Security module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Security configuration.
Start of day: check the permissions needed to run Security.
On shift: use only documented Security commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices6

Assign one main Security owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.

Visual examples0

This module doesn’t have example images yet.

Utilities

Free + Premium

Top

The Utilities module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations.

Quick setup

Free part

Open the dashboard and go to the Utilities module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Utilities configuration and save the changes.

Premium part

Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Free part

Centralise Utilities with less manual work.
Cut staff response times.
Standardise the server’s operating rules.

Premium part

Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Free

/invite

Safe invite.

temporary link.
/remind/remind_list/remind_cancel

Personal reminders.

reminder in 2h.
/poll

Timed poll.

vote on the next activity.
/giveaway

Basic giveaway.

special role giveaway.
/roleinfo/channelinfo/serverinfo

Server information.

review role details.
/ping/uptime

Bot status.

check latency and uptime.
/activity_dashboard/growth_chart

Activity analytics.

review monthly growth.
/avatar/banner

Media lookup.

view an avatar in full size.

Premium

/temp/temp_list/temp_cancel

Temporary messages.

self-destructing notice.
/rank/leaderboard/rewards

Level system.

server leaderboard.

Dashboard configuration examples6

Profile 1: Small community

Goal: make Utilities stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Utilities. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 2: Medium community

Goal: make Utilities stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Utilities. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 3: Large community

Goal: make Utilities stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Utilities. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 4: Support server

Goal: make Utilities stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Utilities. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 5: Gaming server

Goal: make Utilities stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Utilities. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Profile 6: Education server

Goal: make Utilities stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Utilities. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: this profile works fully in base mode; Premium only adds advanced automations.

Usage guides3

Daily use

Scenario: normal Utilities operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Utilities.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Utilities module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Utilities configuration.
Start of day: check the permissions needed to run Utilities.
On shift: use only documented Utilities commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices6

Assign one main Utilities owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.

Visual examples0

This module doesn’t have example images yet.

Backups

Free + Premium

Top

The Backups module lets you set up key server tasks with a clear path. Here you have steps, examples and practical recommendations. It includes the Premium options, shown in this guide.

Quick setup

Free part

Open the dashboard and go to the Backups module from the side navigation.
Check the bot and staff permissions before you start.
Define the channels and roles related to this module first.
Apply a base Backups configuration and save the changes.

Premium part

Run a real test with a staff member.
Check the results in the logs and adjust values if needed.
Leave an internal note so all staff follow the same criteria.
Schedule a weekly review to keep the configuration up to date.

What it lets you do

Free part

Centralise Backups with less manual work.
Cut staff response times.
Standardise the server’s operating rules.

Premium part

Log changes for internal follow-up.
Scale better as the community grows.
Keep a stable experience at peak times.

Commands and examples

Free

/backup create/backup list/backup info/backup delete

Core backup cycle.

create and review backups.
/backup restore/backup schedule

Restore and scheduling.

scheduled daily backup.

Premium

/backup compare/backup export

Compare and export backups.

export JSON for auditing.

Dashboard configuration examples7

Profile 1: Small community

Goal: make Backups stable for daily operation in a small community context.

How to set it up: Dashboard path: Modules > Backups. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 2: Medium community

Goal: make Backups stable for daily operation in a medium community context.

How to set it up: Dashboard path: Modules > Backups. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 3: Large community

Goal: make Backups stable for daily operation in a large community context.

How to set it up: Dashboard path: Modules > Backups. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 4: Support server

Goal: make Backups stable for daily operation in a support server context.

How to set it up: Dashboard path: Modules > Backups. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 5: Gaming server

Goal: make Backups stable for daily operation in a gaming server context.

How to set it up: Dashboard path: Modules > Backups. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Profile 6: Education server

Goal: make Backups stable for daily operation in a education server context.

How to set it up: Dashboard path: Modules > Backups. Enable the module, set up roles and channels, save and validate with a real test.
Suggested values: start in a conservative mode, keep alerts on and review weekly.
Note: Premium note: this profile uses the Premium options to increase control and automation.

Intensive Premium profile

Goal: use every Premium option of Backups.

How to set it up: Dashboard path: Modules > Backups > Premium settings. Enable the advanced features, save, test high-demand scenarios and confirm in the logs.
Suggested values: proactive alerts, live dashboards and automations supervised by staff.
Note: Premium features are marked with a badge, but the whole documentation is visible to everyone.

Usage guides3

Daily use

Scenario: normal Backups operation.

How to use it: Apply the base configuration, use the frequent commands and review the results in the logs.
Expected result: a stable flow without repetitive manual actions.

During an incident

Scenario: a one-off problem related to Backups.

How to use it: Run the control commands, tell the staff and keep a record of what you did.
Expected result: a fast, traceable response.

Weekly review

Scenario: preventive maintenance of the Backups module.

How to use it: Check active settings, clean up outdated configuration and validate permissions.
Expected result: an up-to-date, consistent configuration.

Operations checklist12

Start of day: review the active Backups configuration.
Start of day: check the permissions needed to run Backups.
On shift: use only documented Backups commands.
On shift: log important changes internally.
Peak activity: apply the module’s containment measures.
After an incident: review the history and adjust parameters if needed.
End of shift: leave a short summary for the next staff member.
Weekly review: remove outdated rules and validate channels.
Weekly review: check there are no false positives.
Weekly review: confirm that active Premium features work.
Monthly review: compare the current state with the target configuration.
Monthly review: update the internal guide and owners.

Recommended best practices7

Assign one main Backups owner per shift to avoid gaps.
Make small, measurable changes instead of big ones.
Log every important change with date, reason and owner.
Test changes during quiet hours before rolling them out at peak times.
Combine commands and the dashboard for two ways of control.
Review false positives every week.
Premium badges mark the advanced Backups features; they stay visible to everyone in the guide.

Visual examples0

This module doesn’t have example images yet.

Recommended next step

Start with General settings and Security, continue with Moderation and then turn on Tickets and Automation. Once everything is stable, create a backup and check Statistics every week.

Open the dashboard Talk to support

UltimateBot documentation

Add the bot

Set up basic security

Prepare moderation

Turn on support and automations

Create your first backup

1Access and active server

2General settings

3Security and moderation

4Modules and role permissions

5Plan and Premium

6Staff team

7Tickets, backups and tests

8Final review

Quick setup

What it lets you do

Commands and examples

Profile 1: Small community

Profile 2: Medium community

Profile 3: Large community

Profile 4: Support server

Profile 5: Gaming server

Profile 6: Education server

Daily use

During an incident

Weekly review

Quick setup

What it lets you do

Commands and examples

Profile 1: Small community

Profile 2: Medium community

Profile 3: Large community

Profile 4: Support server

Profile 5: Gaming server

Profile 6: Education server

Daily use

During an incident

Weekly review

Quick setup

What it lets you do

Commands and examples

Profile 1: Small community

Profile 2: Medium community

Profile 3: Large community

Profile 4: Support server

Profile 5: Gaming server

Profile 6: Education server

Daily use

During an incident

Weekly review

Quick setup

What it lets you do

Commands and examples

Profile 1: Small community

Profile 2: Medium community

Profile 3: Large community

Profile 4: Support server

Profile 5: Gaming server

Profile 6: Education server

Daily use

During an incident

Weekly review

Quick setup

What it lets you do

Commands and examples

Profile 1: Small community

Profile 2: Medium community

Profile 3: Large community

Profile 4: Support server

Profile 5: Gaming server

Profile 6: Education server

Daily use

During an incident

Weekly review

Quick setup

What it lets you do

Commands and examples

Profile 1: Small community

Profile 2: Medium community

Profile 3: Large community