Discord server management guide for servers you run for someone else
Managing a Discord server for someone else means setting it up so it still works when you are offline, when a moderator leaves and when the contract ends. This guide covers the settings that matter, in the order you should check them.
Reviewed against Discord's help center and developer docs
Start with roles and permissions
Discord roles work top-down. A member can only act on people whose highest role sits below their own, and the colour you see is the colour of their highest role. Two permissions deserve extra care.
- Administrator grants every permission and bypasses every channel override. Discord's own wording is to assign it "with extreme caution". On a client server, that means the owner and at most one lead.
- Manage Roles lets someone create and edit roles below their own, but only with permissions they already have. Nobody can kick, ban or rename a member with an equal or higher role, even with the permission.
A layout that works for most client servers:
| Role | Key permissions | Who gets it |
|---|---|---|
| Owner | Everything (owner of the server) | The client. Never the agency. |
| Admin | Administrator | One lead on the client side or yours, by agreement |
| Community manager | Manage Server, Manage Roles, Manage Channels, View Audit Log | Whoever runs the server day to day |
| Moderator | Timeout Members, Kick Members, Ban Members, Manage Messages, View Audit Log | Moderation team |
| Helper | Manage Messages in support channels only | Trial moderators, support staff |
| Member | Send messages, no mention @everyone | Everyone who verified |
New roles appear just above @everyone and inherit its permissions as a template, so check @everyone first. Private staff channels are made by toggling Private Channel in the channel's permissions, which removes View Channel from @everyone, then adding the staff roles.
Require 2FA for moderation
With the server-wide 2FA requirement on, staff need two-factor authentication on their own account to use Kick Members, Ban Members, Administrator, Manage Channels, Manage Server, Manage Messages, Manage Roles, Manage Webhooks, Manage Expressions and Manage Threads. It is required for Discovery and worth turning on everywhere else too. A moderator whose password leaks can't then delete channels or ban half the server.
AutoMod, timeouts and the audit log
AutoMod
AutoMod is free on every server, under Server Settings, AutoMod. It has ready-made lists (insults and slurs, sexual content, severe profanity), custom keyword rules of up to 1,000 terms each, a spam content filter and a mention spam limit of up to 50 mentions per message. Each rule can block the message, post an alert to a staff channel and, for custom keywords and mention spam, time the member out. Members with Administrator or Manage Server are always exempt, so test rules from a normal account. The ready-made lists and the spam filter only work in English. Custom keywords work in any language.
Timeouts
A timeout stops someone from sending messages, reacting and joining voice or video. It can last up to 28 days and needs the Timeout Members permission. The reason goes into the audit log, which is a good habit for a team: the next moderator can see why.
Audit log
The audit log shows who changed what: roles, channels, bans, kicks, webhooks. Discord keeps entries for 45 days and only people with View Audit Log can see it. Read it weekly on every client server. It is the fastest way to spot a staff account doing something it shouldn't.
Prevent raids, then plan the response
Discord defines a raid as a large number of users or bots joining at once to disrupt a server. Before one happens:
- Turn on AutoMod with a mention spam limit.
- Remove Mention @everyone, @here and All Roles from every role except staff.
- Set up Raid Protection alerts in Server Settings, Safety Setup. When Discord detects a join raid it alerts your channel and requires a CAPTCHA from new joiners for the next hour.
- Set a verification level and the explicit media filter.
During a raid, in this order:
- 1Pause invites (Server Settings, Invites) or use Security Actions from the server menu to pause invites and DMs between non-friends for a set time.
- 2Turn on Slowmode in the channels being flooded.
- 3Add the raid's phrases to an AutoMod rule with block, alert and timeout.
- 4Raise the verification level to High or Highest until it is over.
- 5Report the raid from the server menu. You need Ban or Kick Members, the desktop app and a Community server.
Keep ownership with the client
Ownership moves from the Members list: right-click the member and choose Transfer Ownership. If the owner has 2FA on, Discord asks for the code. Once done, Discord support can't move it back. If an owner disappears, Discord only transfers ownership on request when the server has 100 active members, the owner hasn't used their account for at least a month, the person asking has been active in the last 30 days and has admin or moderator permissions, and the server isn't monetized. Don't rely on that. Agree who owns the server in writing at the start.
A weekly routine for a managed server
| When | Check |
|---|---|
| Daily | AutoMod alert channel, reports, the rejected verification queue |
| Weekly | Audit log, new roles or webhooks, staff list, a fresh backup |
| Monthly | Server Insights (Community servers), rules still current, onboarding answers still assign the right channels |
| When staff change | Remove the Discord role and the dashboard seat on the same day |
Discord server management tips
- Write the rule down before you enforce it. Members accept a ban when they can see the rule it broke.
- One moderator, one account. Shared logins make the audit log useless.
- Keep bots below staff roles in the hierarchy, and give each bot only what it needs.
- Test every permission change with View Server As Role before members find the gap.
- Save a backup before big changes, not after.
The parts Discord leaves to you
Unlimited staff accounts for free, invited by email, with per-server permissions. Each person sees only the client servers you give them.
Channels, categories, roles, permissions and server settings. Paid plans add messages, emojis, stickers, bans and member role assignments. Backups are kept for life, not rotated out after a short period. Automatic scheduled backups on Plus. If a server is lost, members who verified can be pulled into a new one at one member every 0.98 seconds, on every plan.
FAQs
The questions people ask before they hand a server over.
Something not covered? Ask at help.vaultcord.com.
What is the best way to manage a Discord server?
Give each person the smallest role that lets them do their job, keep Administrator to the owner and one trusted lead, require 2FA for moderation, let AutoMod catch the obvious, read the audit log weekly and keep a recent backup. Most server problems start with one over-powered role.
How long does Discord keep the audit log?
Discord's developer docs say audit log entries are stored for 45 days. If a client wants a longer record, export what you need or send moderation events to a log channel with a bot.
How long can you time someone out on Discord?
Up to 28 days. A timed-out member can't send messages, react, or join voice and video until it ends. The reason you enter is recorded in the audit log.
Can Discord transfer a server back if ownership was given to the wrong person?
No. Discord's help center says its support team can't transfer a server back once ownership has been transferred, so check the member before you confirm.
Is there a free Discord server management bot?
Discord's built-in tools (AutoMod, timeouts, security actions, onboarding) are free and cover a lot. Bots add logging, warnings and verification. VaultCord's free plan covers one server with captcha, account age checks, password protection, backups and unlimited staff seats.