This page is split in two — the first half is what a reader sees when they join and use a community, and the second half is the owner view of managing those members.
For readers — joining a community
The flow
- You land on a community page (e.g.
community.somebrand.comor/en/c/somechannel/community) and click Join community. - If you're not logged in, you're redirected to OmniCon's normal login. After you sign in, you're sent back to the community.
- You fill in three things:
- Display name — required. Your handle in this community. 3–60 characters, letters / numbers / hyphens / underscores. Must be unique within the community.
- Bio — optional, up to 500 characters.
- Avatar URL — optional. If blank, your OmniCon profile image is used.
- Submit and you're in. The community home now has a profile shortcut and a + New post button.
If your display name is taken
The form refuses the submit and shows up to five free alternates ("jane-k-2", "jane-k-3"…) as one-click buttons. Pick one or type your own.
One account, many handles
Your OmniCon account works across every community you join. Your display name, however, is per-community — Jane on a cooking community can be jane-k there and green-thumb-jane on a gardening community, with no relationship visible to other readers.
Editing your profile
From the community home, click your handle (top right) → Edit profile, or visit /community/profile on the community URL. You can change your display name, bio, and avatar. Display-name changes are validated against the community's uniqueness rule.
Leaving
The Edit profile page has a Leave community button at the bottom. Confirmation prompt; on confirm your membership is archived.
Posts you authored stay attributed to your handle (so reader history isn't broken) but you lose access to the community. You can rejoin later with the same OmniCon account — your handle and post history come back if the handle is still free.
For owners — managing members
Open Members from the community admin dashboard at /en/usr/channel/{id}/community/members.
The roster
Paginated table with display name, role, post count, joined date, last active. Filter by role, by keyword (matches display name or, for admins, user id), and toggle to include archived (left) members.
Roles, what each can do
| Role | Posting | Moderating | Notes |
|---|---|---|---|
| Member | Subject to community policy | — | Default for fresh joins |
| Contributor | Always immediate (bypasses pre-approval) | — | Trusted writer; doesn't moderate |
| Moderator | Always immediate | Approve / reject / hide / unhide / ban | Treat as a co-admin |
| Banned | Blocked | — | Soft-disabled; can't post, edit profile, or rejoin |
Changing a role
Each row has an Actions dropdown:
- Reset to Member — for demoting a Contributor or Moderator.
- Make Contributor — promotes a trusted Member to bypass review.
- Make Moderator — gives full mod rights. Has a typed-prompt confirmation on top of the basic confirm because this is the high-impact change.
Every role change is recorded in the audit log (community admin → Audit log).
Bulk-promoting at launch
The Members page has a small form at the top: pick a number, click Bulk promote, and that many random active Members are promoted to Contributor. Capped at 100 per click. Useful when you're seeding a community at launch and want a handful of trusted writers to get going without queuing.
Banning
From the Actions dropdown, click Ban…. Modal opens with a required reason field. Submit and the member's role flips to Banned, the reason is recorded in the audit log, and an email is sent to the member explaining the ban.
Banned members can't post, edit their profile, leave (they're already removed effectively), or rejoin. Existing posts stay attributed.
To unban, the same row's Actions dropdown shows Unban.
Doing it from MCP
Everything on this page is also available as MCP tools — list_community_members, change_community_member_role, ban_community_member, unban_community_member. See MCP — Available tools.