Configuration
Configure moderation behavior, user actions, and notifications for your organization
Open Settings in the Insion dashboard to configure how moderation behaves for your organization. These settings apply to every record and user managed by that organization.
At a glance
| Setting | Default | What it controls |
|---|---|---|
| Email notifications | Off | Emails sent after user actions |
| Appeals | Off | Whether suspended users can submit appeals |
| Test mode | On | Whether moderation results trigger downstream actions |
| Moderation rollout | 100% | Percentage of ingested records selected for moderation |
| Automatic suspension threshold | 1 | Flagged-record count that suspends a user |
Notifications and appeals
Email notifications
Turn on Enable Emails to send configured emails when a user's status changes, such as when they are suspended, reinstated, or banned.
Appeals
Turn on Enable Appeals to allow suspended users to submit an appeal. Insion includes the appeal link in suspension emails when both email notifications and appeals are enabled.
When appeals are enabled, your integration can also retrieve an appeal URL from the user API and create appeals through the API. Learn more in Appeals.
Moderation behavior
Test mode
Test mode is enabled by default. Insion still evaluates and records moderation results, but a changed result does not trigger downstream moderation-status events. That means test-mode results do not automatically suspend or reinstate users, and do not produce moderation webhooks.
Disable test mode only when you are ready for moderation results to drive real user actions and webhooks.
Moderation rollout percentage
Set Roll-out percentage to a number from 0 to 100. It controls the percentage of records submitted through the asynchronous ingest endpoint that are selected for moderation:
| Value | Result |
|---|---|
0 | No newly ingested records are selected at random. |
1–99 | A random sample of ingested records is moderated. |
100 | Every ingested record is moderated. |
This setting does not affect the immediate POST /api/v1/moderate endpoint; that endpoint always performs moderation.
Even at 0%, Insion continues to moderate a record that is already flagged or belongs to a suspended user. This lets the system detect when content becomes compliant again.
Automatic suspension threshold
Set Automatic suspension threshold to a whole number of at least 1. When a non-protected user has at least that many flagged records, Insion automatically suspends them.
For example, a threshold of 3 means a user is suspended after their third flagged record. If their flagged-record count later drops below the threshold, Insion automatically returns a suspended user to compliant status.
Protected users are exempt from automatic actions. Configure protection on the individual user or record, not in organization settings.
Related developer settings
Create an API key
Create a key for your integration.
Set up webhooks
Receive moderation and user-action events.
The Developer area contains organization-scoped API keys and the webhook endpoint. These are configured separately from the settings above: