The audit log
Cogentic records every change to a case against whoever made it. Reading one is not a change, so it leaves no entry.
Every action on a case writes an event: who did it, what they did, what it was about, and when. The case Audit log tab is a view of those events for that case, and the organisation-wide audit page is the same records without the case filter.
What an event records
- Who
The person who did it, under their name as it stood at the time. Work done by the agent is recorded as the agent, never attributed to a person.
- What
The action, from a fixed list rather than free text, so the log can be filtered and counted.
- About what
What it was done to, under the name it had at the time. A case renamed later still reads under the name it had when the thing happened.
- The detail
What changed, specific to that action, plus links to related records.
What the log can prove
| Property | What it actually means |
|---|---|
| Append-only | Nothing can update or delete an audit event once it is written, including Cogentic. |
| Tamper-evident | Each event carries a hash of its own contents, taken when it was written. An event altered afterwards no longer matches it. |
| Isolated per organisation | Your organisation can read only its own events. |
What is not in the audit log
The log records actions taken on a case. It is not a transcript of everything that happened in the product.
- A conversation in Discuss
Asking the agent a question is not an action on the case, so it does not appear as one. If your reasoning matters to the decision, put it where it is recorded: a note, the Plan, or the rationale on the decision itself.
- Reading something
Opening a case, a finding or a source is not recorded. The log holds what was done rather than what was looked at.
- Whether a report was lodged
Submitting a report is an action and Cogentic records it. Lodging it with a regulator happens outside Cogentic, so nothing here can evidence that it was done.
Reading it for a case
The Audit log tab on a case shows that case's events as a timeline. It is the fastest way to answer who changed the assignee, when the decision was made and by whom, and whether anything was altered after the case closed.
- Cogentic
Opened the case and gathered sources
- Cogentic
Recorded 6 findings
- Cogentic
Uploaded a document: supplier invoice
A. Nguyen- A. Nguyen
Work the agent did and work a person did sit in one sequence, attributed separately. That is what lets you answer which parts of a case were machine-produced without reconstructing it from memory.
The data here is invented.
Reading a case leaves no entry, so an auditor sees who changed what and never who looked.
Work done by the agent appears alongside work done by people, attributed separately. That attribution shows which parts of a case the agent produced.
Related
Last checked against the product on .