Community setup & governance

Slack community rules template — a three-section framework for paid communities that members actually read

Q: How do you write community guidelines for Slack?

Write Slack community guidelines in three sections: (1) participation norms — two to four sentences on what an active member looks like (posts at least once a week, responds to others' questions, gives before asking); (2) content standards — a bulleted list of what is not allowed, ordered from most to least common violation (self-promotion outside #promo, posting links without context, solicitation without prior relationship, harassment or personal attacks); (3) moderation policy — a three-step escalation (private DM for first offense, channel warning for repeat, removal with refund for third offense). Keep the total length under 250 words. Write in second person ('you are joining a community of...') using vocabulary your ICP already uses — not legal language. Place the rules in either a pinned post in #announcements or a dedicated #rules channel set to auto-join. Reference the rules once in the day-0 welcome message with a one-sentence framing that positions them as orientation rather than warning: 'Here's how the community works — rules are short, three sections, worth a two-minute read on day one.'

Q: Where do you put rules in a Slack community?

The two viable placements for paid Slack community rules are (1) a pinned post in #announcements, or (2) a dedicated #rules or #community-guidelines channel set to auto-join for all new members. Both have trade-offs. A pinned post in #announcements is more visible on initial join but can get buried as announcements accumulate; it works best if your #announcements channel is low-volume (fewer than two posts per week). A dedicated #rules channel is always directly accessible and signals that rules are a first-class part of community membership, but requires auto-join to ensure new members land there. The worst placement is posting rules only in the welcome message as a wall of text — members who receive a 500-word DM on day zero rarely read past the first 100 words. The best placement is whichever location your community members are most likely to visit in the first 48 hours; for most communities, this is the channel that appears first in the sidebar, which you should control by naming it with a number or symbol prefix (e.g., #0-start-here or #welcome). Do not put rules exclusively in a Notion document or website — most members will never click the link.

Q: How do you enforce Slack community rules?

Enforce Slack community rules with a documented three-step escalation so that enforcement feels consistent and predictable rather than arbitrary. Step 1 (first offense): send a private DM to the member. Reference the specific rule, describe the specific action that violated it, and explain what the correct behavior looks like. Do not call the violation out publicly in the channel — this triggers defensive reactions and creates a spectator dynamic that damages community culture. Step 2 (repeat offense): send a second DM that references the prior conversation. Note that the pattern has repeated. If the community has a #rules or #guidelines channel, link to the specific rule. Be explicit: a third offense will result in removal. Step 3 (third offense or severe single violation): remove the member from the workspace and issue a prorated refund of the current month's fee. Prorating the refund rather than refusing it signals that the removal is about rule enforcement, not revenue, which makes the removal feel fair and reduces reputation risk from the member discussing the experience publicly. The key principle in all three steps is specificity: name the rule, name the behavior, name the consequence. Vague enforcement ('this kind of thing isn't really what we're about here') creates ambiguity about what is allowed and erodes trust in the community's operating norms among members who witness it.

Most paid Slack community rules exist in one of two failure modes: too thin to be useful (“be respectful and keep it relevant”) or so legalistic that no member reads past the first sentence. Neither version does the job rules are actually for — orienting a new member to how the community operates so they can participate confidently from day one. Effective rules for paid communities function as onboarding tools. They establish the community’s operating norms in the voice of the culture, not the voice of a terms-of-service agreement, and they are short enough to be read in under three minutes. This guide covers why most community rules fail, the three-section structure that covers everything without becoming a legal document, the channel placement question, how to reference rules in onboarding without triggering a policed-on-day-one feeling, and when to update rules and how to announce changes.

TL;DR

A paid Slack community needs three categories of rules: participation norms (what active membership looks like), content standards (what is not allowed in any channel), and a moderation policy (what happens when a rule is broken). Keep the total under 250 words. Write in second person, in the community’s own vocabulary, not legal language. Post in a pinned #announcements post or a dedicated auto-join #rules channel. Reference once in the day-0 DM, framed as orientation (“here’s how it works”) not warning (“here are the rules”). Update when a new pattern of rule-breaking emerges or when an existing rule has been enforced more than three times in a month.

Why most paid community rules fail at their primary job

The primary job of community rules is not to prohibit bad behaviour — it is to orient new members to how participation works so they know what to do on day one. A member who understands the operating norms of a community is more likely to participate, more likely to contribute at a level that creates value for others, and more likely to stay. A member who reads rules as a list of things not to do receives only information about what the community is not, which is a less useful orientation than knowing what it is.

The two failure modes in the wild share the same root cause: rules written for the operator rather than the new member.

Too thin: “Be nice, stay on topic, no spam.” Three words per rule gives a new member no information about what participation actually looks like. What does “on topic” mean in a community for growth marketers? Does it include tactical questions about specific tools, or only strategic questions? Is a link to a podcast episode “on topic” if it’s related? The absence of specificity forces new members to infer norms by observing existing behaviour — a process that takes weeks and discourages participation in the meantime. Thin rules are also unenforceable: when a violation happens, “you weren’t being nice” is a subjective and contentious enforcement argument, not a clear reference to a defined standard.
Over-legalistic: eight paragraphs of liability language and definitions. Rules written by a lawyer (or by an operator who copied a SaaS terms-of-service document) are not written for the person who will read them: a member who just paid $99 and is opening Slack for the first time. Dense legal prose signals institutional distance, which is exactly the wrong signal for a community that is selling belonging. When the first communication a new member sees from the community is a wall of legal boilerplate, the implicit message is that the operator views members as potential liabilities rather than as the people the community exists to serve. Read rates on over-legalistic rules documents are very low — operators who have checked their link-click data from day-0 welcome messages typically find fewer than 15% of new members click through to an external rules page.
Framed entirely as prohibitions (“do not” language throughout). Rules that consist only of “do not” statements tell a new member about the threats the community is protecting itself from, not about the culture the community is trying to create. The reader finishes the document feeling warned rather than welcomed. A rules document that opens with a participation-positive statement (“this is a community of operators who share what’s actually working”) before listing prohibitions uses the same space to do two jobs: set expectations about what active participation looks like, and define what will get someone removed.

The three-section structure: what to include and what to leave out

Three sections cover everything a paid Slack community rules document needs to do. Each section is short — two to four sentences or a bulleted list. The total document should take under three minutes to read.

Section 1

Participation norms

What active membership looks like in this community. Two to four sentences, second person, positive framing. Describes the contribution behaviour the community is optimised for.

Example: You are joining a community of paid community operators who share what’s working, ask hard questions, and respond when others ask for help. Active members post at least once a month, give context when they ask questions, and respond to at least one other member’s thread per week.

Tells a new member what participation looks like before they’ve done anything wrong. Most rules documents skip this entirely.

Section 2

Content standards

What is not allowed in any channel. A bulleted list of specific behaviours, ordered from most to least common. Each bullet names the behaviour concretely, not abstractly.

Example bullets: Self-promotion or product pitches outside #promotions. Links posted without a sentence of context. Solicitation of a business relationship without a prior public exchange. Personal attacks or harassment. Off-platform recruiting or lead collection.

Concrete beats abstract: “links without context” is enforceable; “low-quality content” is not.

Section 3

Moderation policy

What happens when a rule is broken. A three-step escalation that names the consequence for each offense level. Makes enforcement predictable and removes ambiguity.

Example: First offense: private DM naming the rule and the specific action. Second offense: DM noting the pattern; explicit warning that a third will result in removal. Third offense (or any single severe violation): removal from the workspace and a prorated refund of the current month’s fee.

Including the refund policy signals that enforcement is about rule compliance, not revenue, which reduces public dispute risk.

What to leave out: definitions of terms, explanations of how Slack works, copyright or IP clauses, dispute resolution language, age restrictions, or any content that would be more appropriate in your Terms of Service on your website. Rules posted in Slack are a cultural document, not a legal one. Legal language belongs in your Terms of Service; Slack rules belong in the voice of your community.

The copy-paste template

This template is designed to be edited to match the vocabulary and culture of your specific community. Replace bracketed items with your actual community name, channel names, and any norms specific to your ICP. The structural shape — three sections, total under 250 words — should remain.

Slack community rules template — three sections, copy-paste ready

How [Community Name] works

You’re joining a community of [ICP description: e.g., paid community operators / growth-stage founders / B2B content marketers] who [what they share and how they participate: e.g., share what’s actually working, ask specific questions, and respond when others ask for help]. Active members post at least once a month, give context when asking questions, and reply to at least one thread per week from someone they don’t already know.

What’s not allowed in any channel

— Self-promotion, product pitches, or affiliate links outside [#promotions or equivalent channel name]
— Links posted without at least one sentence of context or commentary
— Soliciting a business relationship without a prior public exchange in the community
— Off-platform recruiting, lead collection, or scraping member contact details
— Personal attacks, harassment, or publicly calling out a member in a way designed to embarrass
— Sharing another member’s private messages or DM conversations without their consent

How moderation works

First offense: private DM from [operator name] naming the specific rule and the specific action. Second offense: DM noting the pattern with an explicit note that a third will result in removal. Third offense, or any single severe violation (harassment, solicitation, data scraping): removal from the workspace and a prorated refund of the current month’s fee. If you’re not sure whether something is allowed, DM [operator name] before posting — the answer will always be faster than a rule violation notice.

Edit the bracketed items. Do not add more sections. Keep total word count under 250. Post as a pinned message or in a dedicated #rules channel, not as a PDF or external link.

Where to post the rules: channel placement

Two placements work for paid Slack community rules. Two do not. The choice between the two working options depends on your community’s specific channel setup and posting cadence.

Option A

Pinned post in #announcements

Works when #announcements is low-volume — fewer than two posts per week. New members who auto-join the channel see the rules near the top of the message history. The pin ensures it stays accessible. The limitation is that in higher-volume announcement channels the pin becomes one of many pinned items and loses salience.

Set the rules as the oldest pinned item in the channel so it anchors the channel history and reads as foundational.

Recommended for most communities

Option B

Dedicated #rules or #0-start-here channel

Works when you want the rules to be the first channel a new member lands in. Set the channel to auto-join and name it with a prefix that sorts it to the top of the Slack sidebar (e.g., #0-start-here or #rules). Post the rules once in the channel with no other messages, so the entire channel is the document.

The dedicated-channel approach makes rules more visible for new members who scroll the sidebar before reading any messages.

Recommended for communities with high new-member volume

Avoid

Wall of text in the day-0 welcome DM

Including the full rules document in the automated welcome message is the lowest-read placement. Members who receive a 400-word DM on day zero — when they have not yet done anything, when they are still orienting to the workspace — skim or ignore everything past the first paragraph. The welcome DM should reference the rules with a single sentence and a link to the channel where they live.

Avoid as primary placement

Avoid

External link (Notion, website, PDF)

Members who need to click out of Slack to a Notion page or your website to read the rules will rarely do so. Link-click rates from community welcome messages to external rules documents are typically below 15%. Rules need to be readable in the place where the community lives. An external link is appropriate for your full Terms of Service; community operating norms belong in-platform.

Avoid as primary placement

How to reference rules in onboarding without making new members feel policed

The framing of the rules reference in a day-0 welcome message has a significant effect on how new members read and respond to the document. There are two versions of the same reference: one that reads as orientation and one that reads as warning. They contain the same information. The difference is entirely in framing.

Warning framing (avoid): “Before you get started, please read the community rules in #rules. Violations may result in removal.” This construction — before you do anything, read the rules or face consequences — positions the new member as a potential rule-breaker before they have done anything. It sets a defensive rather than welcoming tone on day one.

Orientation framing (use this): “Here’s how the community works — #rules has a two-minute summary of participation norms and how moderation works. Worth a quick read on day one so you know where everything lives.” This construction frames the rules as information the new member will find useful, not as a warning. The phrase “so you know where everything lives” positions the rules as orientation material, not a legal prerequisite to participation. The phrase “two-minute summary” sets an accurate expectation about time investment and implicitly communicates that the operator respects the member’s time.

The difference in read rates between these two framings is significant. Communities that use orientation framing in their day-0 welcome message report 40–60% of new members confirming they read the rules (via a reply trigger in the welcome message) versus 15–25% for warning framing. The rules document that the operator spent time writing is more likely to do its job when the invitation to read it is framed as helpful rather than compulsory. For the full anatomy of a welcome message that gets replies, see the guide on Slack community onboarding checklist.

When to update rules and how to announce changes

Rules should be updated reactively — when a new pattern of rule-breaking has emerged that the current rules do not cover clearly, or when an existing rule has been enforced more than three times in a month on the same type of violation. Proactive rules updates — writing rules for situations that have not yet occurred — usually produce documents that are longer than needed and include clauses that are never enforced.

Trigger

A rule has been enforced more than three times in a month for the same violation type

If the same rule is being violated repeatedly, it is either not clear enough or not prominent enough. Edit the rule to name the specific behaviour more concretely, or move the rules channel to a higher-visibility placement.

Trigger

A new violation type is occurring that the current rules do not address

Add a bullet to the content standards section naming the new behaviour. Do not add a new section. Update the timestamp on the rules post.

Trigger

A rule enforcement led to a public dispute or member complaint

If a member challenged an enforcement and others sided with them, the rule or the escalation description is likely ambiguous. Clarify the specific language that was contested before the next enforcement needs to happen.

Avoid

Updating rules after every session of self-reflection on community governance

Rules that change frequently signal instability. Members in paid communities are paying for a reliable, consistently-managed experience. Quarterly review at most; only update when a concrete trigger exists.

How to announce changes: Post in #announcements with a single sentence naming the change and why: “Updated the content standards rule on self-promotion to clarify that case studies are welcome in #wins without pre-approval — three members asked about this in the past month so the rule was ambiguous.” Explain the change in plain language. Do not post a versioned changelog of the rules document — this signals bureaucracy, not community. If the change is significant (adding a new enforcement step, changing the removal policy), send a DM to members who were enrolled before the change.

Announcing why a rule changed rather than just that it changed serves two purposes: it shows members that enforcement is evidence-based rather than arbitrary, and it demonstrates that the operator is paying attention to patterns in how the community is being used. Both signals increase trust in the community’s governance. For how channel architecture intersects with community norms and the onboarding experience, see the guide on Slack channel structure for paid communities.

Rules and the onboarding sequence: how they connect

Rules on their own do not produce the behaviour they describe. A member who reads a well-written participation norms section does not automatically post more because they read the phrase “active members contribute at least once a month.” Rules set expectations; the onboarding sequence creates the first behaviour. The relationship is that rules define the operating environment and the onboarding sequence provides the first action that places the new member inside it.

The connection works best when the day-0 welcome message references the rules with the orientation framing described above, then provides a single specific first action that is directly consistent with the participation norms the rules describe. If the participation norm is “active members post in their area of focus,” the day-0 action should be: “Introduce yourself in #intros — one sentence on what you’re working on right now.” The rule and the action point in the same direction, and the new member’s first experience of the community is one of consistency between what it says it is and what it asks them to do. For the complete onboarding flow and how the day-0 message connects to day-3 and day-7 touches, see the Slack community onboarding checklist. For the engagement metrics that tell you whether the rules and onboarding sequence are producing the behaviour they describe, see Slack community member engagement rate.

Try Foothold

Foothold automates the day-0/3/7 onboarding sequence — the mechanism that turns rules-readers into first-time posters. The day-0 DM references your rules with orientation framing, gives one specific first-action ask, and includes a reply trigger that activates the connection offer. The day-3 nudge goes only to members who haven’t posted yet. The day-7 report shows you who activated and who the operator should personally follow up with. Public pricing. One-click Slack OAuth. 14-day trial, no credit card.

Join the early-access waitlist →

Not sure whether your community’s onboarding is the weak point or the rules are? Take the 2-minute Onboarding Health Check — five questions, a 0–50 score, and the top three fixes for your specific number. No email gate.

Frequently asked questions

What rules should a paid Slack community have?

A paid Slack community needs three categories of rules: participation norms (what active membership looks like), content standards (what is not allowed in any channel), and a moderation policy (what happens when a rule is broken, in three escalation steps). Effective rules for paid communities function as an onboarding tool, not a threat document — the participation norms section is the most read and the most impactful because it tells a new member what contribution looks like before they’ve had a chance to figure it out by observation. Rules should be under 250 words total, written in second person, in the vocabulary your ICP uses rather than legal language. The three most important specific rules to include in the content standards section are: no self-promotion outside a designated channel, no links without context, and no solicitation without a prior public exchange. The moderation policy should include a prorated refund for the month of removal, which signals that enforcement is about rule compliance rather than revenue and reduces public dispute risk.

How do you write community guidelines for Slack?

Write Slack community guidelines in three sections totalling under 250 words. Section one: participation norms — two to four sentences on what an active member looks like, in positive framing (“active members post at least once a month and give context when asking questions”). Section two: content standards — a bulleted list of specific prohibited behaviours, ordered from most to least common, with each bullet naming the behaviour concretely rather than abstractly. Section three: moderation policy — a three-step escalation from private DM to warning to removal, including the refund policy for removed members. Write in second person throughout. Do not use legal language — write in the vocabulary your community members use for their work. Post the guidelines in-platform (pinned in #announcements or a dedicated auto-join #rules channel), not in a Notion document or external link. Reference the guidelines once in the day-0 welcome message with orientation framing: “Here’s how the community works — #rules has a two-minute summary worth reading on day one.”

Where do you put rules in a Slack community?

The two viable placements are a pinned post in #announcements (best for low-volume announcement channels with fewer than two posts per week) or a dedicated #rules or #0-start-here channel set to auto-join for all new members (best for communities with high new-member volume where you want rules to be the first channel a new member lands in). Both work. The two placements to avoid are including the full rules text in the day-0 welcome DM (member attention in the day-0 DM is limited; use the DM to reference the rules channel, not replicate them) and posting an external link to a Notion document or website page (link-click rates from Slack to external rules pages are typically below 15% — rules need to live where the community lives).

How do you enforce Slack community rules?

Enforce rules with a documented three-step escalation that makes consequences predictable and removes ambiguity. Step 1 (first offense): private DM naming the specific rule and the specific action that violated it — never call out violations publicly in the channel. Step 2 (repeat offense): DM noting the pattern and explicitly stating that a third offense will result in removal. Step 3 (third offense or severe single violation): remove the member from the workspace and issue a prorated refund of the current month’s fee. The prorated refund is important: it signals that removal is about rule enforcement, not revenue, which makes the removal feel fair and reduces the likelihood of the removed member complaining publicly. In all three steps, be specific: name the rule, name the behavior, name the consequence. Vague enforcement (“this isn’t really what we’re about here”) creates ambiguity about what is allowed and erodes other members’ trust in how the community is governed.