Blog
How to Set Up a Discord Server and Manage It with Bots
Published:
1. Create the server: template or from scratch
A new server is created with the plus (+) button on Discord's left sidebar. If you pick one of the ready-made templates, such as gaming, friends or a school club, a few channels come with it; if you choose to create your own, you start with an empty server. A template is a quick start, but you will still need to reshape the channels to fit your own structure.
The account that creates the server becomes its owner, and ownership does not pass to anyone else unless the owner transfers it. If you are opening the server for a business, a gaming community or a brand, create it with an account you will keep using for a long time and that has two-factor authentication turned on.
2. Group channels into categories
Channels come in two kinds, text and voice, and are grouped under categories. Keep the number of channels low: a new member should see at a glance where to write. A common layout is an info category for announcements and rules, a general chat category, a few topic channels and voice rooms.
Categories have another benefit: when you set permissions on a category, the channels under it take those permissions as synced. That way you do not have to set permissions one by one each time you add a channel.
3. Plan roles and permissions
Roles are the real structure of a server. The @everyone role is the base permission set for every member; start there and only allow what everyone needs. Then create roles such as admin, moderator and member, and give each one just enough permission for its job.
Role order matters: a person or a bot can only manage roles that sit below their own highest role. A bot that hands out roles needs its role placed above the roles it gives; otherwise the bot looks like it is working but cannot assign anything.
The Administrator permission grants every permission and also overrides channel restrictions. Give it only to a few people you truly trust. If a particular channel needs a different rule, use that channel's own permission settings; for example, turning off message sending for members in the announcements channel.
4. Safety settings: verification level and AutoMod
The verification level is set in the Safety Setup section of Server Settings. The higher the level, the more a new account must meet before it can post: a verified email, an account that has been on Discord for a while, a waiting period on the server or a verified phone number. On a public server, a higher level cuts down on ads and spam from freshly created accounts.
AutoMod is the automatic moderation built into Discord: it can catch keywords you choose, spam-like messages and mass mentions. It can block the message, post an alert to a channel your moderators watch or put the person in a timeout. You do not need a separate bot for this.
The server owner can require two-factor authentication for moderation actions, so even if one of the staff accounts is taken over, it is harder to use it for mass deletes or kicks. The Audit Log records who deleted which channel, who gave a role to whom and who kicked whom; when something goes wrong, it is the first place to look.
5. Community features and welcoming new members
If the server is going to grow, you can turn on the Community feature in the settings. Discord then asks for a rules channel, an updates channel and minimum settings for verification and the content filter. In return you get tools such as announcement channels, a welcome screen and Onboarding.
With Onboarding, a new member answers a few questions, for example which game they play or which topic they care about, and roles and channels open up automatically based on the answers. That can remove the need for a separate bot for simple role assignment, and your rules are shown before the member starts posting.
6. What bots take over
Discord's own tools cover the basic structure; bots take over the repetitive work. The most common jobs are a welcome message, getting a role with a button or a reaction, moderation that keeps a record of warnings and penalties, opening support tickets, posting notifications from a game server, a website or a channel into the right place, and a level system.
Ready-made bots do most of these jobs. If you need a rule specific to your server, a link to your own website or game server, or your own database, a bot written for your server is the better fit. We explained how a bot is written step by step in How to Make a Discord Bot.
7. What to watch when adding a bot
To add a bot to a server you need the Manage Server permission. On the authorisation screen the bot lists the permissions it asks for; keep only the ones it needs, and do not grant Administrator to a bot that does not need it. Giving broad permissions to a bot from a source you do not know is like handing over the keys to your server.
You can limit who can use a bot's commands, and in which channels, from the Integrations section of Server Settings; for example, allowing penalty commands only for the moderator role and fun commands only in one channel. Remove bots you no longer use; every bot can reach your server as far as the permissions you gave it.
If you use a bot written for you, never share its token and never push it to GitHub inside the code. If the token leaks, someone else can control the bot and, through its permissions, your server; if you suspect a leak, reset the token right away.
Let's set up your server and bot
We do Discord server setup together with the channel and role structure, and we write moderation, role, support ticket or notification bots made for your server. Tell us what you need, and we will pin down the scope for your custom Discord bot together.
Related service
Bot DevelopmentStarting from $30