Telynt / Documentation

Search documentation

Search platform contracts, developer guides, package manuals and the Technology Consulting & Delivery solution.

Browse documentation

Ethics and Compliance Review

Ethics & Compliance — Reviewer Audit

On this page

Navigation: Intelligence → Ethics & Compliance → Reviewer Audit
Access: restricted audit or oversight permission
Primary audience: compliance oversight, security, internal audit, and designated investigators

Purpose

Reviewer Audit provides the immutable user-facing record of access and decisions inside the restricted ethics workspace. It supports investigation of unusual access, missing reasons, decision changes, exports, and procedural completeness.

Scope controls and indicators

Period sets the audit window. Event Type filters evidence access, decision change, assignment, export, handoff, note, or other event. Actor selects authorized reviewers or services. Object limits findings, cases, policies, or exports.

Audit Events is total activity. Evidence Access counts controlled opens. Unusual Access shows events meeting an investigation rule, not confirmed breaches. Decision Changes counts altered decisions while preserving prior state.

Immutable reviewer audit log

Each row shows timestamp, actor, event, object, reason code, result, and reference. Filters never change the underlying record. Selecting an event opens permitted metadata and linked activity.

Unusual-access investigation

The investigation panel presents the observed pattern, actor authorization, time window, network or device context, assigned cases, reason-code status, exports, and current investigation state. It explicitly distinguishes anomalous behavior from confirmed security breach.

Supporting analysis

Audit event mix shows access, decision changes, escalations, exports, and other events. Audit completeness checks actor identity, reason codes, object links, and immutable checksum. Audit actions provides investigation, export, and security-case work.

Actions

  • Filter and open an audit event.
  • Start or continue an unusual-access investigation.
  • Request missing reason codes where procedure allows.
  • Export an authorized audit package.
  • Link a security event or close an investigation with rationale.

Confirm that the rule was triggered, examine access purpose and assigned scope, and avoid treating unusual timing or volume as proof. Record findings separately from raw events and escalate only under the applicable security or compliance procedure.

Cases, Audit & Security, and Restricted Analytics.