---
title: Best Practices
url: https://docs.kaltura.com/docs/rich-media-cms-apis/content-moderation/moderation-best-practices
---

## Best Practices

- **Enable moderation before going live** — Set `moderateContent=true` on the account so new uploads start in `PENDING_MODERATION` rather than auto-approving
- **Use AI moderation as a first pass** — Run REACH moderation tasks on upload, then have human moderators review only flagged content to reduce queue volume
- **Separate entry and category moderation** — Use entry-level moderation for global content policies and category moderation for channel-specific editorial standards
- **Monitor the moderation queue daily** — Entries stuck in `PENDING_MODERATION` or `FLAGGED_FOR_REVIEW` are invisible to viewers; stale queues block legitimate content
- **Bridge AI results to entry status** — REACH auto-action only affects `categoryEntry` status; configure a webhook to call `baseEntry.approve`/`reject` based on `moderationOutputJson` results
- **Use strict policies for user-generated content** — Apply `strict_moderation_v1` or custom policies with all text and visual rules for UGC-heavy accounts
- **Set up notification webhooks** — Configure email notifications for `CONTENT_MODERATE_APPROVE_REJECT` permission holders so moderators are alerted when new content enters the queue