Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kansato.com/llms.txt

Use this file to discover all available pages before exploring further.

Report lifecycle

Reports use these API/database statuses:
StatusMeaning
OPENIngested; not yet in active review (or reopened after resolve).
IN_REVIEWActively being worked—for example after AI enrichment crosses a confidence threshold, escalation, or moderator assignment.
RESOLVEDClosed with a resolution (content or account action recorded).
DISMISSEDClosed without violation (false positive, duplicate, out of scope, etc.).
CLOSEDTerminal closed state where your workflow uses it (for example after final disposition).
Reopening a resolved report sets status back to OPEN or IN_REVIEW depending on queue assignment (see SDK unresolve behavior). Dismissed reports follow your product rules for reopen.

Severity

Each report reason has a severity hint: LOW, MEDIUM, or HIGH. The queue uses these to prioritize.
  • HIGH maps to critical-style treatment in the queue.
  • LOW / MEDIUM map to elevated treatment.
Configure hints per reason in Settings → Moderation.

Reports as the unit of work

Moderation work is tracked per report. Each report has its own status, assignment, tags, and history. There is no separate “case” entity grouping multiple reports.

Dismiss reasons

SDK and API accept these dismiss reason codes:
ReasonUse when
false_positiveNot a valid violation.
duplicateSame issue already tracked.
out_of_scopeOutside your policy.
not_actionableNo proportionate action available.
otherCatch-all.

Escalation targets

TargetTypical use
safetyTrust & safety queue
legalLegal / policy escalation
senior_moderatorSenior review
Escalation records the target for audit and, unless the report is already resolved, moves it into the active review pipeline (IN_REVIEW).

Queue

The moderation queue reads organization reports (for example GET /api/v1/organizations/{orgSlug}/reports). Common filters:
  • Project — limit to one integration surface.
  • Open vs done — active reports are typically OPEN or IN_REVIEW.
  • Severity — derived from reason hints (HIGH vs others).
Exact fields and filters are in the API reference and OpenAPI spec.