Audit Logs
Zentake records an audit trail of actions taken through the API and the
dashboard. Each entry captures, at minimum: the action taken, the
object it was taken on, the team, and (where applicable) the
user or patient involved, plus a free-form additional_data
payload and a source.
Actions that get logged
The audit system tracks a fixed set of action types, including:
| Category | Actions |
|---|---|
| Record lifecycle | CREATED, UPDATED, DELETED, ARCHIVED, MERGED, DUPLICATED, REASSIGNED |
| Intake flow | SENT, RESENT, COMPLETED, VIEWED, VISITED |
| Data access/output | EXPORTED, DOWNLOADED, WEBHOOK |
This means actions on Patients, Forms, Packets, Responses, and PDF Documents are logged.
Audit log entries are not exposed through the public REST API described
in the API Reference. There is no
GET /v2/audit-logs endpoint. Audit history is a dashboard feature.
Scoping
Every audit entry is tied to the team it occurred under, consistent with Zentake's Team-scoped isolation model, one team cannot see another team's audit history.
Coverage and integrity
- Coverage. Every PHI-touching action is recorded — actions on Patients, Forms, Packets, Responses, and PDF Documents all produce an audit entry.
- Tamper-evidence. Audit entries are append-only; they are written as an immutable record rather than being edited or overwritten in place.
Access and export
Audit history is available through the Zentake dashboard. Self-service export of audit history for a team's own records is not available today; contact Zentake if you need an audit-history export for compliance purposes.