Content moderation checks conversation inputs and model outputs against a moderation service. You point the platform at an OpenAI-compatible service and choose which categories to enforce on each surface.

Where to find it#

Open Content moderation in the admin console. Only superadmins can manage the moderation service and policies. Other administrators see a note that stats are under Statistics and events are under Logs.

The page has two sections: Moderation service and Moderation policies.

DEEIX Chat admin content moderation

Enable content moderation#

  1. Turn on Enable content moderation.
  2. Configure the service fields below.
  3. Select at least one moderation category.
  4. Click Save.

When the switch is off, moderation does not run, but the service and policy settings are kept. You must save an API key before you can enable moderation or test the connection.

Configure the moderation service#

FieldRequiredNotes
Enable content moderationYesTurns moderation on or off.
Moderation service URLYesAn OpenAI-compatible service root, a /v1 URL, or a full /moderations URL.
Moderation modelYesThe model used for text and image moderation.
Moderation API keyYesWrite-only. Leave blank to keep the current key, or enter a replacement and save.
Moderation timeoutWhen enabledTotal wait for one check, an integer from 1 to 60 seconds.
Moderation max concurrencyWhen enabledModeration tasks that can run at once, an integer from 1 to 64.
Moderation queue capacityWhen enabledMaximum queued moderation tasks, an integer from 1 to 4096.

Click Save to persist changes. If a numeric field is out of range, the error names the field and its allowed range.

Test the connection#

  1. Save the service settings first. The test button is disabled while there are unsaved changes.
  2. Click Test connection.
  3. Read the result. It runs a Text probe and an Image probe, each marked valid or invalid with its latency.

If the probe fails, you see "Connection test failed" with the error message. Fix the URL, model, or API key and test again.

Configure moderation policies#

Policies decide which checks run on which surface. The four surfaces are:

SurfaceWhat it moderates
Input textPrompts and text sent in the current turn.
Input imageUploaded images used in the current turn.
Output textText generated by the assistant in the current turn.
Output imageGenerated images shown as reply attachments.

For each surface:

  1. Open the category dropdown.
  2. Select the categories to enforce. Use Select all to select every category.
  3. Click Save.

The dropdown lists the categories reported by the moderation service. The trigger shows how many are enabled, for example "Enabled 3/12", or "Disabled" when none are selected.

Policies are disabled until content moderation is on. Hovering the disabled selector shows "Enable content moderation before configuring moderation policies." At least one category must be selected before moderation can be enabled, or you see "Select at least one moderation category before enabling content moderation."

Where results appear#

  • Statistics shows moderation counts and latency by day, direction, modality, category, and result.
  • Logs → Moderation events (superadmins only) shows each check with its result, direction, modality, latency, and decrypted text or isolated images.

See Logs for the event filters and detail view.

Troubleshooting#

What you seeWhat to check
"An API key is required before content moderation can be enabled."Save a moderation API key.
"Select at least one moderation category before enabling content moderation."Select at least one category on any surface.
"{field} must be an integer from {min} to {max}."Fix the out-of-range timeout, concurrency, or queue capacity.
"Connection test failed"Check the service URL, model, and API key. Confirm the service is reachable.
Test button is disabledSave the service settings first; the test runs only against saved values.
Policy dropdown is greyed outTurn on content moderation first.
"Only superadmins can manage moderation policy and service settings."Ask a superadmin to make the change.
  • Logs for moderation events and their details.
  • Billing if the moderation model incurs usage cost.
  • Models for the model catalog.