Content and avatar review

This page covers only Lumoswitch community-content and avatar review. It does not describe safety policy for model prompts or responses. When COMMUNITY_CONTENT_MODERATION_ENABLED is enabled, community content and avatars are sent to the configured content-safety provider before publication. Administrators can inspect review records and override the final status.

When the feature is disabled, the business service allows the content and records the moderation provider as disabled. Provider failures follow the instance's configured allow/deny failure mode; production deployments should choose and document that mode explicitly.

Automatic avatar review

After an avatar is uploaded, Lumoswitch verifies its file type, size, and dimensions before sending it to the configured content-safety provider:

1. An automatically approved avatar becomes active immediately.
2. An avatar marked rejected or requiring review is not shown publicly.
3. Provider errors allow or reject the upload according to the instance's configured failure mode.
4. Every upload keeps a separate record containing the automatic result, risk labels, confidence, provider, and review time.

Administrator review page

Platform administrators can open Console → Avatar review to see every avatar record, not only pending submissions. The page shows:

• the automatic result and effective final status;
• the content-safety provider and risk labels;
• the submitting user, image properties, and submission time;
• the administrator who changed the result, the adjustment time, and any rejection reason.

An administrator can set any record to approved or rejected. A manual decision has the highest priority and is never replaced by the original automatic result. If the currently active avatar is rejected manually, Lumoswitch restores the user's most recent avatar that is still approved, or uses the default avatar when none is available.

Community content

Community reviews, discussions, replies, shared prompts, and shared skills are reviewed before they become public. Their review records remain in the database, but rejected content does not appear on community pages. Discussion images are reviewed after object-storage upload and before they are attached to a post.

Platform administrators can open Console → Community content review to inspect every community text and discussion-image review. Each record includes its content type, preview, automatic result, final status, provider, risk labels, and administrator. Administrators can set a record to approved or rejected; the manual result takes priority and immediately changes whether the content appears on public community pages.

Community page visibility

Administrators can use Console → Module visibility → Community pages to control Activity, Discussions, and the Creation Library separately for users and administrators. A hidden page is removed from navigation and direct visits are redirected to another visible community page. Discussion detail pages are unavailable when Discussions is hidden.

Boundary with inference content safety

Client model requests go directly to the Lumoswitch inference service. The Lumoswitch Control API does not receive or moderate prompts or responses. Whether model input and output pass through a guardrail, moderation service, or provider safety policy depends on the actual Lumoswitch Runtime and final provider configuration. Do not promise inference moderation until it is configured and verified.

Review records and privacy

Review records are intended only for platform safety, appeals, and administrator review. Administrators should follow least-privilege access and must not copy or disclose user images or identity details.