Moderating an online community - roles, permissions and rules that hold up

Every community reaches the size where good intentions stop being enough. The first fifty members police themselves. The first five hundred do not. Somewhere in between, you need structure: roles that say who can do what, permissions that make the structure real, and rules that a stranger can read in thirty seconds and understand.

This guide covers how to set that up before you need it - and how to run it once you do.

Start with the smallest structure that works

The most common moderation mistake is building an elaborate hierarchy on day one. Ten roles, colour-coded, with carefully graded permissions, for a community of forty people. It looks organised. In practice it creates confusion about who to ask for help and gives you a structure you have to maintain forever.

Start with three levels:

• Everyone. The default. Can read, talk, react, join voice.
• Moderators. Can delete messages, remove members, and manage the day-to-day.
• Owner and admins. Can change the structure itself - channels, roles, permissions.

That is enough for the first several hundred members. Add a role when you have a concrete, repeated need for it, not because it might be useful later. A good test: if you cannot name the specific thing this role lets someone do that they cannot do today, you do not need it yet.

Permissions are about channels, not just people

Most people think about permissions as a property of a person: this member is trusted, that one is new. The more useful frame is that permissions are a property of a place. What matters is not "can Sam post?" but "who can post in announcements?"

A few patterns that hold up well:

• Announcements. Everyone can read; only admins can post. This is the single highest-value permission override in most communities - it makes one channel reliably signal rather than noise.
• Introductions and general. Fully open. New members need somewhere to speak immediately, or they never speak at all.
• Staff channels. Hidden from everyone but moderators. Not for secrecy - for focus. Moderation conversations that happen in public turn into arguments about moderation.
• Project or topic channels. Open to read, open to post, but explicitly scoped. Scope is a form of moderation: it lets you redirect rather than delete.

In Glade, permissions are set per role and can be overridden per channel, so you can keep a single simple role list and still shape each room individually. The role says what someone generally can do; the channel override says what happens here. Keep the role list short and let the overrides do the detailed work.

Write rules people can actually remember

Long rule lists are written for the writer, not the reader. They exist so a moderator can point at clause 7b after the fact. Nobody reads them in advance, which means they prevent nothing.

Write five rules. Make each one a sentence. Make each one about behaviour, not topics:

1. Treat people as if you will have to talk to them again tomorrow.
2. Keep conversations in the room they belong to.
3. No harassment, slurs, or targeting individuals.
4. No spam, scams, or unsolicited advertising.
5. Moderators have the final call; take disputes to DMs, not to the channel.

Then write the part most communities skip: what happens when someone breaks them. A warning, then a temporary removal, then a ban is a perfectly good ladder. Publishing it does two things - it makes enforcement feel fair rather than arbitrary, and it means your moderators do not have to invent a response under pressure.

Build the moderation team before you need it

The worst time to recruit moderators is during an incident. You end up promoting whoever is online, which is how communities end up with moderators chosen for availability rather than judgement.

Recruit from people who are already doing the work informally: the ones who answer newcomers' questions, who de-escalate arguments without being asked, who report problems rather than pile on. Being active is not the qualification. Being steady is.

When you bring someone on:

• Give them the permissions and nothing else. No secret expectations. Write down what they are responsible for.
• Agree on the boundaries of a solo decision. Deleting spam: act alone. Banning a long-standing member: talk first.
• Give them a place to talk. A staff channel where they can ask "is this over the line?" prevents both overreach and paralysis.
• Let them be off duty. A moderator who feels permanently on call quits in three months. Rotate, and say out loud that nobody has to answer everything.

Moderate the boring things first

Dramatic incidents are rare. What actually erodes a community is the slow stuff: the channel that has drifted off-topic for a month, the member who is never quite rule-breaking but always slightly exhausting, the unanswered questions from newcomers piling up in general.

Three habits that do more than any ban:

• Answer newcomers within the hour. A first message that gets no reply is usually a member's last message.
• Redirect early and lightly. "This is a great thread for #projects" costs nothing and keeps rooms legible.
• Close what is dead. An archived channel is a signal that the space is tended. Eight abandoned channels tell every visitor that nobody is home.

Handle conflict in the open, decisions in private

When something goes wrong publicly, the response should be visible - a short, calm message in the channel that the behaviour is not acceptable and the conversation is moving on. What should not be public is the deliberation: how long the ban is, whether it is a first offence, what the member said in DMs.

The reasoning is simple. Public deliberation invites the community to relitigate every decision and turns your moderators into defendants. Public outcomes keep everyone confident that things are being handled. Say what happened, not why you argued about it.

And when you get one wrong - you will - say so plainly and reverse it. A community that has seen its moderators correct a mistake trusts them far more than one that has never seen them admit to any.

Let the structure grow with the community

Revisit the setup roughly every time your membership doubles. At each step ask three questions:

• Is any channel doing two jobs? Split it.
• Is any role doing nothing? Remove it.
• Is any single person a bottleneck? Spread the permission.

Structure should always be slightly behind your growth - tight enough to be legible, loose enough that people are not waiting on permission to participate. Over-engineered communities feel like offices. Under-moderated ones feel like a room where someone is shouting. The work is staying in between.

Glade gives you roles with custom colours, per-channel permission overrides, and a member list that shows only the people who can actually see the room you are in - so the structure you design is the structure people experience. Create a free account and set your House up before you need it.