OmniCon 2.0.22 — Community feature

2.0.22 lands the biggest single change since OmniCon launched — the Community feature. A channel can now host its own community where readers log in with their existing OmniCon account, get a per-community profile, and post their own content. Rolling out gradually across tenants — if you'd like it enabled on your channel sooner, drop us a note.

What "Community" means in OmniCon

A Community attaches to one Channel. The channel owner enables it and decides:

• Who can post. Members, contributors (trusted, bypass review), or moderators (trusted + can review).
• What approval new posts need. Open (post immediately), every post reviewed, first N posts per member reviewed, or members-only.
• Who can read. Public to any visitor, or members-only.
• Where it lives. If the channel has a verified custom domain, the community lives at community.theirbrand.com/community — readers never see "omnicon" in the URL unless they go digging.

Members get their own profile (display name, bio, avatar) per community. Same OmniCon account works across every community a member joins, but their handle is per-community — Jane might be jane-k in a cooking community and green-thumb-jane in a gardening one.

What you get

• Member experience — Join (with helpful collision-recovery handle suggestions when a name is taken), profile read & edit, leave, re-join. Drag-and-drop avatar reusing the article main-image flow we shipped in 2.0.20.
• Posting and moderation — every state in the lifecycle: Pending → Published / Rejected / Hidden, with author-facing banners on every state and a moderator queue that's one click to approve and one form to reject (with a required note shown to the author). Posts in non-Published states never appear in public search.
• Custom-domain support — a verified custom domain serves the community at your-domain.com/community alongside your existing channel site.
• Role management and bans — bulk-promote a handful of trusted readers to Contributor at launch, demote, ban with a required reason, unban. Full audit trail for every action.
• SEO and discovery — sitemap and RSS feeds at /community/sitemap.xml and /community/feed.xml.
• Email touchpoints — members get a SendGrid email when their post is rejected, when their role changes, or when they're banned, so they're never left guessing.
• Dashboard tiles — at-a-glance counts on the community admin: total members, members this week, pending review queue depth, posts this week.
• MCP tools — twelve new tools covering CRUD, members and roles, the moderation queue, and post approve / reject / hide. Agents can drive the whole community admin without touching the portal.

Also in 2.0.22 — small but nice

• Breadcrumb on the article create/edit form. Previously edit was a navigation dead-end — your only escape was the browser Back button. Now the same breadcrumb pattern as the article details page sits at the top so you can bail back to the channel without losing your place.