A community is enabled per-channel by the channel owner. It's a one-time setup — once on, it stays on until you disable or archive it. You can change the settings any time afterward.
Where to find it
From your channel dashboard at /en/usr/channel/{id}, click the Community action button (the people icon next to Edit channel). If your channel doesn't have a community yet, you'll see an empty-state with a single Enable community button. Click it to open the setup form.
Settings to pick
Display name
Shown on the community home and the join page. Defaults to the channel's title — fine to keep, or set something more community-flavored ("MyRecipes Cooks", "Acme Builders").
Tagline (optional)
One-line subtitle next to the display name. Useful for setting tone — e.g. "Share what you're cooking this week."
Post policy
The most important decision. Four options, plain-English labels in the form:
- Open — members post immediately. Best for tight-knit, trusted communities.
- New members reviewed — first N posts per member go to moderation; after that they bypass review. Sensible default for most public communities (catches spam-on-arrival without permanently policing regulars). Default N is 3.
- Every post reviewed — every post (from non-Moderators) goes to the queue. Slow but airtight; good for high-stakes spaces.
- Members only — site is fully gated. Only logged-in members can read or write. Good for paid memberships or private launches.
Moderators always bypass the review queue regardless of policy.
Pre-approval threshold (N)
Only used by New members reviewed. Default 3. The count is per member — a member's fourth post auto-publishes once their first three are approved.
Default role on join
What new joiners are assigned. Almost always Member. The other option, Contributor, is for invitation-only / private communities where every joiner is implicitly trusted.
Posts readable without joining
If on (default), anyone visiting the community URL can read posts. Joining is only required to write.
If off, the entire community site is gated to logged-in members. Useful for private spaces. (Distinct from the Members only post policy, though both gate visibility — pick whichever describes your case.)
Welcome message
Optional. HTML allowed. Rendered on first-join landing and on the community home. Good place to say what kind of posts belong, link community guidelines, or thank early members.
What happens after you click Enable
- The community is created on your channel.
- You land on the community admin dashboard with stats tiles (members, pending review, posts this week) and links to Members, Moderation, Audit log, and Settings.
- The public community URL is live immediately:
- On the default host:
/{culture}/c/{your-channel}/community - On a verified custom domain:
{your-domain}/community(see custom-domain routing)
- On the default host:
Changing settings later
From the community dashboard, click Settings. Same form as the enable flow — change anything, save. The audit log records what changed and who changed it.
Disabling vs deleting
Use Disable community on the dashboard's danger-zone area to soft-disable. The public site 404s for non-admins; members and posts are kept. Re-enabling restores everything.
There is no permanent delete in v1 — too easy to lose history. If you genuinely need to wipe a community, contact us.
Next
Once enabled, see members and roles for who can join and how to manage them, or moderation queue and post policy for running the review pipeline day-to-day.