Getting Started
This guide gets Lockie invited, connected to the Dashboard, and ready for day one moderation.
Lockie is built around a dashboard-first setup. You can still use commands in Discord, but most server configuration should be done from the Dashboard so your staff team can review settings without memorizing command syntax.
Before you start
You will need:
- A Discord server where you can manage the server.
- Permission to invite bots and authorize slash commands.
- A staff log channel, such as
#mod-logsor#lockie-logs. - A protection log channel for Anti-Spam, Anti-Scam, Anti-Dox, Anti-NSFW, and similar events.
- A clear staff role list so Lockie knows who should be trusted with moderation and dashboard access.
Recommended first install
Many server owners invite Lockie with broad permissions first, confirm everything works, then tighten permissions later. If you do this, make sure Lockie's role stays above the roles it needs to moderate.
Step 1: Invite Lockie
Use the official invite link:
When Discord asks for permissions, keep the applications.commands scope enabled. Without it, slash commands may not appear.
After inviting, confirm:
- Lockie appears in your member list.
- Lockie is online.
- Lockie's role is above the members and roles it needs to moderate.
Step 2: Open the Dashboard
Most configuration is managed here:
Then:
- Sign in with Discord.
- Choose the correct server.
- Check that Lockie is already inside the server.
- Open the server page.
If the server is missing, make sure you are signed into the correct Discord account and that you have the required Discord permissions on that server.
Step 3: Enable the core plugins
Start with the plugins your server actually needs.
Moderation
Use this for manual staff actions, case logs, warnings, mutes, kicks, bans, purges, mass actions, and Recent Cases.
Recommended setup:
- Set a moderation log channel.
- Choose which staff roles can use moderation tools.
- Review how cases should appear in logs.
- Test one safe action in a private channel.
Locking
Use this for channel locks, unlocks, lock role behavior, and Maintenance Mode.
Recommended setup:
- Choose whether locks should affect
@everyone, a selected role, or a configured lock role. - Set the lock role if your server uses one.
- Test locking and unlocking in a non-critical channel.
Anti Check
Use this for automated protection modules.
Common modules include:
- Anti-Spam
- Anti-Scam
- Anti-Dox
- Anti-NSFW
Recommended setup:
- Enable one module at a time.
- Set the action for each module, such as delete, timeout, kick, ban, or log only if your version supports it.
- Configure allowlists and blocklists.
- Watch the protection log channel while tuning.
Embed Builder and Welcomer
Use these when you want cleaner server messages.
- Embed Builder creates reusable dashboard embeds.
- Welcomer sends new member messages to the channel you choose.
Step 4: Configure logs
Logs are what make Lockie easy to audit. At minimum, configure:
| Log type | Recommended channel | Used for |
|---|---|---|
| Moderation logs | #mod-logs | Warns, mutes, kicks, bans, purges, mass actions |
| Protection logs | #security-logs | Spam, scam, dox, NSFW, risky content |
| Action logs | #staff-actions | Dashboard saves, commands, template changes, App Activity |
App Activity
If your dashboard includes App Activity, connect it with the Action Logs Channel under the Moderation plugin. This helps staff see who changed settings, used commands, or updated templates.
Step 5: Tune allowlists and blocklists
Anti-Scam and Anti-Dox controls can use whitelist and blacklist entries.
For standard servers, the usual limit is:
| Control | Whitelist limit | Blacklist limit |
|---|---|---|
| Anti-Scam | 15 entries | 15 entries |
| Anti-Dox | 15 entries | 15 entries |
Premium may unlock higher limits, unlimited checks, and extra dashboard controls depending on the plan.
Use allowlists for trusted items and blocklists for content your server never wants posted. Keep the lists clean and review them after false positives.
Step 6: Test safely
Try these simple checks:
Bot responsiveness
/pingLogging
Run one safe moderation action in a private test channel and confirm a log appears.
Locking
In a non-critical channel, test:
/channel lock-everyone
/channel unlock-everyoneAnti Checks
Turn on one protection module, confirm the log channel is set, then review the first few logs before increasing actions.