Terminology

Insion uses a few moderation terms in specific ways. Use this glossary to understand what they mean in the dashboard, API, SDKs, and webhooks.

Core concepts

Appeal

A request from a suspended user to have their suspension reviewed. An appeal can be Open, Approved, or Rejected. Approving an appeal reinstates the user; rejecting it leaves the suspension in place. Banned users cannot appeal. See Appeals.

Ingestion

Creating or updating a record or user in Insion from your application. Ingesting a record through the ingest endpoint can queue it for asynchronous moderation. Ingestion does not itself mean that the content was flagged or that action was taken against a user.

Moderation

The evaluation of a record against your organization's active rules. A moderation produces a Compliant or Flagged result and records which rules matched. One record can have multiple moderations over time as its content changes or it is evaluated again.

Organization

Your workspace in Insion. Records, users, rules, API keys, webhooks, and configuration belong to an organization and are isolated from other organizations.

Record

A piece of content submitted by your application, such as a post, comment, message, profile, or listing. A record has your clientId, an Insion ID, an entity describing its kind, and a current moderation status. A record can optionally be associated with a user.

User

An account or person in your application whose content is sent to Insion. An Insion user is not a member of your Insion dashboard team. Users connect related records and can be suspended, reinstated, banned, protected from automated actions, or allowed to appeal.

Rules and decisions

Compliant

For a record, Compliant means its latest moderation did not match an active rule. For a user, it means no suspension or ban is currently applied. The two statuses are related but separate: a user can have a compliant status while one of their records is still flagged if automatic actions are disabled or have not reached the configured threshold.

Flagged

A record status meaning the latest moderation matched one or more active rules. Flagging a record can contribute to an associated user's automatic suspension, depending on your configuration.

Preset

A preconfigured moderation category supplied by Insion, such as Harassment or Spam. Adding a preset gives your organization a ready-made rule and detection behavior. See Rules & presets.

Rule

A moderation policy that describes content your organization wants Insion to detect. A rule can come from an Insion preset or be custom-defined. When a record is flagged, its moderation result identifies the rules that matched.

User actions

Automatic suspension threshold

The number of flagged records associated with a non-protected user that triggers an automatic suspension. If the count later falls below the threshold, Insion can automatically return the user to Compliant. The minimum value is 1.

Banned

A user status representing a stronger, intentional restriction than suspension. Banned users cannot submit appeals and are not automatically reinstated when their flagged-record count falls.

Protected

A setting that exempts a user or record from automated moderation actions. Use it for trusted users or content that should not be automatically acted on. Protection does not mean “already moderated,” and it is configured separately for each user or record.

Reinstated

A user who has been returned from Suspended to Compliant, either after an approved appeal, a manual action, or an automatic status change.

Suspended

A user status that temporarily restricts a user because of moderation results or a manual action. Suspended users can appeal when appeals are enabled. Your application is responsible for enforcing the status it receives from Insion.

API and processing

Asynchronous moderation

Moderation that happens after an ingest request has returned. Your application does not wait for the final decision in the request; use webhooks or retrieve the record later to receive the result. The POST /api/v1/ingest endpoint uses this model.

Client ID

The stable identifier assigned by your application to a record or user and sent as clientId in the API. It is distinct from the ID that Insion assigns. Record ingestion and deletion use your record's client ID, while retrieve endpoints use the Insion ID.

Entity

A label chosen by your application to describe a record's kind, such as post, comment, or message. It helps you organize and filter records; it is not a moderation result.

Insion ID

The identifier Insion assigns after creating a record, user, moderation, or other resource. API responses generally return it as id. Do not confuse it with the clientId supplied by your application.

Moderation pending

A record state indicating that asynchronous moderation has been queued but has not yet produced its final result. A pending record may still expose an earlier moderation status until the new evaluation finishes.

Moderation rollout

The percentage of newly ingested records selected for asynchronous moderation. It can range from 0% to 100%. It does not affect the synchronous moderation endpoint, and some previously flagged records or records belonging to suspended users may still be evaluated. See Configuration.

Passthrough

An option on synchronous moderation requests that evaluates content without retaining the record's name or content, or the associated user's email, name, or username. Insion still returns the moderation decision.

Synchronous moderation

Moderation that returns its decision in the same API request. The POST /api/v1/moderate endpoint uses this model and always performs moderation, regardless of the moderation rollout setting.

Test mode

A safe evaluation mode that still runs moderation and stores results but prevents changed results from triggering downstream user actions and moderation webhooks. Test mode is enabled by default. See Configuration.

Webhook

An HTTP request Insion sends to your configured endpoint when an event occurs, such as a moderation or user-status change. Webhooks let your application react to asynchronous results without repeatedly polling the API. See Set up webhooks.