How to set up a Discord server people actually use

Most Discord servers are set up in ten minutes and then quietly reorganised four times over the following year. The reorganising is the expensive part, because channels carry history and roles carry permissions, and both are awkward to move once people are using them.

Here is a structure that survives, and the two decisions that are genuinely hard to reverse.

Start with fewer channels than you think

The instinct is to make a channel per topic so nothing gets lost. What actually happens is that twelve channels get one message a week each, the server looks dead, and people stop opening it.

A channel earns its place by being busy. Start with:

• one general — where everything happens
• one voice
• one for links/media, if your group shares a lot of them
• one admin-only

Add a channel when a conversation is genuinely crowding out another one. Splitting a busy channel is easy; merging two dead ones means telling people the thing they were using is gone.

Categories are for permissions, not for tidiness

A category's real job is that channels inside it inherit its permissions. That makes categories the right tool for "this group of channels is for this group of people" and the wrong tool for "these channels are vaguely related".

If you find yourself making a category with one channel in it, you wanted a channel.

The two decisions that are hard to undo

1. Whether @everyone can see the server by default.

If your server is public and @everyone has View Channel on the top-level category, everything you add later is public unless you remember to close it. Closing it afterwards means auditing every channel you have made since. Decide this on day one.

2. Your role hierarchy.

Discord permissions are resolved by role position, and a bot cannot manage a role above its own. Get the order right before you have twenty roles:

Admin
Moderator
[bots]          ← above every role a bot must manage
Boosters / special
Members
@everyone

⚠ Bots go above the roles they hand out and below the ones they must not touch. A rank role sitting above your bot will look fine, sell fine, and then fail with a permissions error at the one moment it matters.

Verification, if the server is public

An open Discord accumulates spam accounts. A verification gate — a button that grants the Member role, or a short question — removes almost all of it, because the bots doing the spamming do not press buttons.

The trade is one extra click for every genuine person, so it is worth it for a public server and not worth it for eight friends.

Give people a reason to come back

This is the part no permissions diagram covers. A server that is only a chat window competes with every other chat window. The ones people open daily have something happening — a levelling system with visible progress, a counting channel, a starboard collecting the best moments, a movie night that recurs.

None of that has to be elaborate. It has to be visible.

What to automate, and when

Do not automate anything on day one. Run the server manually for a fortnight and notice which things you do repeatedly — that list is your automation list, and it is different for every group.

Common ones, roughly in the order people reach for them:

1. Welcome and roles — greeting new members and handing out the Member role.
2. Moderation logging — a record of deletions and edits, because "I'm sure I saw a message" is otherwise unanswerable.
3. Levelling — the most common way to make participation visible.
4. Statistics — knowing whether the server is growing or quietly shrinking.

There are good bots for each of these individually, and there are bots that do several. Which route makes sense depends mostly on how many you would end up running — that arithmetic is in what a Discord bot stack costs.

We built Asbern to be the second kind, and it is one subscription for all of it — but a server running three free bots happily does not need to change anything.