1. Capabilities work together
Participation is not one universal feature switch. Each capability must be available on the Stage's platform plan and separately enabled for that Stage.
| Capability | Available from | What it includes |
|---|---|---|
| Community | Vibeler Scale | Community Studio, discussion-channel posting contract, and the member directory |
| Moderation | Vibeler | Pending-post review, returned-text filters, and Stage bans |
| Gamification | Vibeler Scale | Optional points, levels, badges, and leaderboard experiences |
2. Community Studio
Community Studio summarizes the Stage's existing community state. It is not the place where all participation rules are currently configured.
- Summary
- Shows the current member count, number of creator-post and community-discussion channels, and number of non-empty activity sections.
- Channel links
- Opens each creator-post or community-discussion channel and displays its stored Public or Members-only state.
- Activity feed
- Can show non-empty Pinned, Active Discussions, Upcoming Events, New Members, and Latest Content sections.
- Channel drawer
- Admins with channel-management permission can create, rename, reorder, move, or delete channel groups and channels.
3. Member post lifecycle
Non-admin members can post only in a Community discussion channel, and only when all of these checks pass:
- The member is signed in, has an active Stage subscription, and is not banned.
- The member is entitled to view the channel and the Stage has Community enabled and available on its plan.
- The channel is a Community discussion channel with member posting enabled.
| State or action | What happens |
|---|---|
| Save draft | Keeps the post unpublished and out of the review queue. |
| Submit | Requests publication. The channel's stored approval setting decides the next state. |
| Publish directly | Publishes immediately when the channel does not require approval. |
| Review | Keeps the post unpublished and pending until a permitted moderator acts. |
4. Review & filters
When approval is required, the Moderation queue shows pending member posts with their author, timestamp, title, and text preview. Approving publishes the post and notifies its author. Rejecting keeps it unpublished and can include a reason of up to 512 characters.
The moderation settings also expose a default profanity toggle and a custom word-or-phrase list. The backend currently masks matching text when returning Community discussion posts and comments; it does not reject the submission.
5. Member directory
- Who can open it
- An authenticated, non-banned active Stage member or an admin with community-management permission.
- Who appears
- Only members who enabled “Show me in the member directory” on their Stage profile.
- Browse controls
- Display-name search, points/newest/activity sorting, and incremental loading. The current audience page loads 24 profiles at a time.
- Member profile
- A Stage-specific display name, bio, current focus, up to ten interests, and directory-visibility choice.
Points, levels, badges, and leaderboard context are meaningful only when Gamification is also enabled. They are not promised by the Community capability alone.
6. Bans & comments
Stage admins with community-member permission can search for a username, ban an eligible user, list current bans, and unblock a user from Moderation Studio. An active ban blocks that user from Stage access and interactions until they are unblocked.
A comment author can delete their own comment. A Stage admin with community-member permission can also delete it. That operation permanently removes the selected comment and its reply tree; the current product has no restore workflow.
7. Current self-serve limits
- The current channel drawer exposes channel visibility, member posting, and approval controls. Subscription-plan channel access is configured from the subscription tier editor.
- An auto-created Community discussion channel currently defaults member posting off.
- Community Chat is a post-based discussion surface, not realtime chat or direct messaging.
- There is no member-report queue, warning history, appeal workflow, community-role builder, or community-guidelines builder.
- A guest-author record provides content attribution; it does not grant Stage access or publishing permission, and it is not a community role. Add a collaborator as a Stage admin when they need to create or manage content directly.