Every document in Recognito carries an audit trail of field edits and approver actions. The History tab in Studio shows it in chronological order, with a "View changes" diff link on each entry.
History is read-only — you can't edit or delete entries. Recognito records the events as they happen.
Open any document in Studio and switch to the History tab.
Each event records its timestamp, its actor, and what changed. The actor is often a system component rather than a person — the trail above shows the OCR service writing the initial values, post-processing running, a Mapping workflow filling derived fields, and the system adding an approver, all within eight seconds of upload.
Field-change events carry a View changes link that opens the before-and-after diff.
History persists for the life of the document. Even after it is Approved and Exported, the record stays.
A field value changed — either via extraction (the engine writing initial values), a Mapping workflow (a rule populating a derived field), or a user editing the field manually. The entry records which field and what the change was.
You'll see many of these on any document. The first batch shows extraction populating the initial state; the next shows any Mapping rules that fired; further ones show edits the assignee made during review.
History is a per-document trail. It doesn't give you an org-wide or project-wide audit log of every action across every document. If you need cross-document audit coverage, talk to your account manager.
When rejecting or approving a document, you can optionally leave a short comment. This is useful for recording "why" decisions — "Rejected: vendor not authorized for this PO" — that the action itself doesn't capture.
Use comments for non-obvious decisions
A rejection without a comment forces the next person to guess your reasoning. A one-sentence comment on a non-obvious decision saves your colleagues real time later.
Comments & history
History is read-only — you can't edit or delete entries. Recognito records the events as they happen.
Where History lives
Open any document in Studio and switch to the History tab.
Each event records its timestamp, its actor, and what changed. The actor is often a system component rather than a person — the trail above shows the OCR service writing the initial values, post-processing running, a Mapping workflow filling derived fields, and the system adding an approver, all within eight seconds of upload.
Field-change events carry a View changes link that opens the before-and-after diff.
History persists for the life of the document. Even after it is
ApprovedandExported, the record stays.Event types
Several event types show up in History. The most common ones:
Document updatedA field value changed — either via extraction (the engine writing initial values), a Mapping workflow (a rule populating a derived field), or a user editing the field manually. The entry records which field and what the change was.
You'll see many of these on any document. The first batch shows extraction populating the initial state; the next shows any Mapping rules that fired; further ones show edits the assignee made during review.
Approver AddedA user was added as an approver on the document — either because a workflow rule populated
approvers_N_M, or because an admin manually assigned them.Approver RemovedThe inverse of Approver Added. The user is no longer in the approver list for the document.
Other events
The full list of event types isn't published. If you see an entry you don't recognize, the description usually makes its meaning clear.
What the History tab is for
Three common uses:
What History is not
History is a per-document trail. It doesn't give you an org-wide or project-wide audit log of every action across every document. If you need cross-document audit coverage, talk to your account manager.
Comments
When rejecting or approving a document, you can optionally leave a short comment. This is useful for recording "why" decisions — "Rejected: vendor not authorized for this PO" — that the action itself doesn't capture.
Use comments for non-obvious decisions
A rejection without a comment forces the next person to guess your reasoning. A one-sentence comment on a non-obvious decision saves your colleagues real time later.
What's next