On this page
Audit, history, and record changes
Use Trazadera Golden table auditing and history to review supported record changes without exposing private operational detail.
Golden separates audit events, which explain supported changes, from history records, which retain records needed for operations such as merge undo. Enable the corresponding table controls before data changes occur. Neither reconstructs activity that happened while its control was disabled.
Enable the controls
auditable and history are separate table settings. Auditing can also be
enabled or disabled on an existing table by an administrator. Disabling it keeps
retained events but opens a gap; re-enabling does not fill that gap. See
Audit controls for the procedure.
History is not a version of every business field after every edit. Whether a record enters history depends on the operation and configuration. In particular, merging with history retains contributing records, and deleting with history retains the deleted record. Without retained contributors, merge undo cannot recover them. See Resolve duplicates.
Inspect audit and history
Read audit events through the dedicated table record endpoint. An ADMIN or
STEWARD needs access to the record; VIEWER cannot read its audit timeline.
For Aurelia, set the service URL and an authorized bearer token, then request:
curl --fail-with-body --silent --show-error \
--header "Authorization: Bearer ${GOLDEN_TOKEN}" \
"${GOLDEN_URL}/api/tables/sample_customer/records/CRM-0001/audit"
The response contains events. Ordinary record responses omit _audit, even
when expanded. Audit events are read only through the dedicated endpoint. An empty event list does not prove
that auditing has always been enabled or that the record never changed.
Read retained history through table record queries
with type=HISTORY. History metadata describes the recorded operation and
relationships; it does not replace the audit timeline. See
Record metadata.
Preserve useful attribution
Give each person a distinct user and each integration its own token. Record a meaningful comment where the operation supports one. Shared credentials weaken attribution. Establish retention and evidence-export requirements with your service agreement; the existence of a timeline alone is not a retention promise.