Audit Log

Core Compliance

Audit Log is the immutable operational history of your ERP activity. It records who did what, when, and to which resource, then lets you export and verify that evidence later.

This page is functional-first: it explains how administrators and compliance teams should use Audit Logs in day-to-day operations and external audits.

Who should use this

Tenant administrators who need operational traceability.
Compliance/security teams preparing ISO/SOC2/GDPR evidence.
Operations managers investigating data changes and user actions.

What Gets Logged

Each event stores context fields that support both troubleshooting and compliance proof.

Field	Description	Example
timestamp	UTC timestamp for the event.	2026-04-30 13:41:23
action	Event name/category.	sequence.edited
severity	Risk/relevance level.	info / warning / critical
actor_display	User/service identity that triggered the event.	Cubix Admin (cubix)
actor_ip	Origin IP when available.	127.0.0.1
resource_type	Logical model type affected.	CubixSequence
resource_display	Human-readable resource label.	Lead sequence LEAD/2026
changes	Before/after payload for changed fields.	{"before": {...}, "after": {...}}
metadata	Extra context (e.g. company id, reason code).	{"company_id":"...","reason":"manual_edit"}

Export Workflow

Export generates a compliance PDF from the currently filtered dataset and includes an integrity fingerprint.

Apply filters

Choose severity/date/event/actor/resource filters in Audit Log list. Export always reflects the active filter state.

Click Export

The system generates a PDF with records, metadata, filter summary, and an integrity section.

Store evidence

Share the exported PDF as an audit artifact. Keep it with ticket/case references for future traceability.

Best practice: include export timestamp, filter scope, and ticket id in your compliance evidence register.

Verification Link

Every export includes a verification URL. It re-runs the same filtered query and recalculates the hash to check integrity.

Open verification URL

Use the URL printed in the export footer (requires authenticated admin access).

System recomputes hash

CubixOne replays the exact filter set and computes SHA-256 over canonical record payload.

Interpret result

Verified means exported content still matches live records under that scope. Mismatch means the artifact or context changed.

Verification confirms consistency against current database state for the same filter scope. It does not “freeze” database history after export.

Filter parameters used by verify/export

Parameter	Used in verify	Used in export
severity	Yes	Yes
event	Yes	Yes
actor	Yes	Yes
resource_type	Yes	Yes
date_from / date_to	Yes	Yes
time_from / time_to	Yes	Yes
q + field (legacy list search)	No	Yes

Integrity Model

CubixOne uses deterministic serialization + SHA-256 hash over exported records to provide tamper-evident proofs.

Same record set + same order + same serialization => same hash.
Any modified value changes the computed hash.
Verification URL carries the original hash and filter context.

Known limits

Verification is scope-dependent (filters/date range/severity/event/actor/resource type).
If data legitimately changes after export, verification mismatch is expected.
Admin permissions and tenant/company scoping apply to both export and verify operations.

Operational Checklist

Use this for internal controls and external audits.

Control	Action	Evidence
Scope control	Apply explicit filters before export.	PDF filter summary line.
Integrity proof	Run verification URL after export.	Verify page result with timestamp.
Access control	Ensure only tenant admins/platform staff can export/verify.	Role matrix + access logs.
Retention process	Archive exports by policy window.	Retention register / archive index.
Incident workflow	Tie audit extracts to incident tickets.	Ticket links + export filenames.

FAQ

Why do some events not appear?

Most often due to scope/filters (tenant, severity, field search, date window) or because the action type is outside selected criteria.

Why can verification fail?

Typical causes: different filter scope, data changed after export, invalid hash parameter, or insufficient permissions to access full dataset.

Does export change if filters change?

Yes. Export is always generated from the active filters. Different scope means different record set and different hash.

Is verification a digital signature?

Verification is tamper-evidence by deterministic hashing of records and context, not a third-party timestamping/signing service.