Every channel can host a Community — a space where readers log in with their existing OmniCon account, pick a per-community handle, and post their own content alongside yours. You decide who can post immediately, what needs review, and who's allowed to moderate.
When to use it
A Community fits when you want to turn one-way publishing into a two-way conversation. Common shapes:
- User-contributed content. A cooking site lets readers post their own recipes. A travel blog lets readers share trip reports. The host curates; the community produces.
- Q&A or support. Customers post questions, your team and trusted members answer.
- Member areas behind a brand. A private community visible only to logged-in members, sitting on your custom domain.
If you just want comments on articles, that's a different feature. Community is for letting readers create their own posts as first-class content.
How it fits with the rest of OmniCon
A Community attaches to one Channel. It's not a separate workspace — it lives inside the channel's URL space (or, with a verified custom domain, on your own host) and shares the channel's authors, search, and admin model.
- Authentication is OmniCon's. No separate community signup. The same login works across every community a reader joins, but their display name is per-community — Jane can be
jane-kon a cooking community andgreen-thumb-janeon a gardening one. - Posts are articles underneath. Search, RSS, sitemap, and the article editor all "just work" on community posts. The difference is the moderation lifecycle layered on top.
- Custom domains are reused. If your channel already has
community.yourbrand.com, the community lives atcommunity.yourbrand.com/communityautomatically.
Roles in a community
| Role | Can do |
|---|---|
| Member | Default for fresh joins. Posts are subject to your community's post policy. |
| Contributor | Trusted member — bypasses pre-approval. Can't moderate. |
| Moderator | Approves, rejects, or hides posts. Can ban abusive members. Their own posts publish immediately. |
| Banned | Soft-disabled. Can't post, edit a profile, or rejoin. |
Post moderation states
Every community post goes through one of four states:
- Pending — submitted, waiting for moderator review. Visible only to the author.
- Published — approved (or auto-published when policy allows). Public.
- Rejected — moderator declined. Author still sees it with the reason; can edit and resubmit.
- Hidden — was published, then pulled offline. Same author-side experience as rejected.
The author can always edit and resubmit a rejected or hidden post — content isn't destroyed, just made not-publicly-visible.
Where to next
- Enabling a community on your channel — the one-time setup.
- Members and roles — joining, profiles, role management.
- Moderation queue and post policy — running the review pipeline.
- Custom-domain routing — running a community on your brand's domain.