Publish community policies
Admins can maintain Privacy, Terms, and Community Guidelines through the existing policy editor. Public and tenant policy routes keep those documents reachable in the relevant context.
Set policies, review access and events, resolve reports and appeals, and separate human responsibility from plan-based AI assistance.
Access and moderation decisions affect real participation. They need clear policies, appropriate roles, a review record, and understandable outcomes. Sapeans groups different review types without pretending they are identical, and keeps human responsibility distinct from any AI-assisted moderation available through a plan.
Admins can maintain Privacy, Terms, and Community Guidelines through the existing policy editor. Public and tenant policy routes keep those documents reachable in the relevant context.
The Review queue groups community joins, Circle joins, and Space access. Reviewers see the request type and available decision rather than treating every pending item as the same membership action.
Events waiting for publication can appear as their own review group, preserving event identity, creator context, and the specific approval responsibility.
Reported posts, comments, and members are separated from unban requests and other appeals. Authorised reviewers can dismiss, action, or resolve using the controls and permissions exposed by the current product.
Admins, moderators, members, pending members, banned members, and blocked relationships receive different actions. Community deactivation is reversible and preserves data while pausing member access and public discovery.
Publish policies, access behavior, roles, and participation rules.
Requests, event submissions, reports, and appeals enter the appropriate queue group.
An authorised reviewer opens the detail and uses the valid action for that request type.
Membership, publication, content, ban, or appeal state updates the surfaces that depend on it.
Community admins and moderators receive different management powers; Circle and Space managers remain narrower still.
Membership, Events, Content reports, and Appeals remain distinguishable while sharing one operational queue.
AI moderation is mentioned only according to the current Sapeans and Enterprise plan descriptions and never replaces the described human decision path.
Core roles, policies, requests, reports, and review behavior follow current community permissions. AI moderation is listed in current Sapeans copy, with configurable AI moderation in Enterprise; no autonomous or guaranteed outcome is claimed.
Current groups include community, Circle, and Space access; event review; reported posts, comments, and members; and unban appeals.
No. Admins have broader community settings and role-management powers. Moderators retain the review and moderation capabilities currently granted by the product.
This page does not claim autonomous decisions. AI moderation is a plan-based capability, while review actions and role responsibility remain explicit.
No. The current reversible deactivation flow pauses member access and discovery without deleting members, posts, events, configuration, or billing records.