System Audit Trail
Immutable record of all actions performed on the platform. Essential for compliance, traceability, and responding to external audits.
System Audit Trail
The Audit module is the institutional memory of Rela AI. It automatically and immutably records every significant action that occurs on the platform: who created what, who modified what, exactly when, and what it looked like before. When an external audit arrives or when you need to investigate why something changed, this record has all the answers.
What is it for?
Industrial plants operate under regulatory frameworks that require traceability: ISO 9001 requires control of changes in monitored processes, industrial safety standards require records of access and modifications to critical procedures, and food or pharmaceutical industry regulations require evidence of who did what and when.
Rela AI's audit record automatically meets these requirements without anyone having to remember to document anything:
- Every LOTO procedure created or approved is recorded
- Every change to an agent's configuration is recorded
- Every task created, modified, or closed is recorded
- Every access to sensitive data is recorded
If someone asks "who changed the alarm threshold on compressor C-01 last Tuesday?", the audit record has the exact answer.
How does it work?
Each significant operation automatically generates an audit entry with:
| Field | Description |
|---|---|
| Action | What was done: create, modify, delete |
| Resource type | What was affected: agent, task, asset, user, rule, etc. |
| Resource ID | The unique identifier of the affected element |
| Actor | Who did it — user, automated system, or API key |
| Previous state | How the element looked before the change |
| New state | How it looked after the change |
| Timestamp | Exact date and time in UTC |
| Verification hash | Cryptographic signature that guarantees the record was not altered |
Audit records are immutable: they cannot be modified or deleted. They form a verifiable chain where each record includes a signature based on the previous record — if anyone attempted to alter a record, the chain would break and become detectable.
The record is also non-intrusive: it is generated in the background without affecting system performance. If the audit record were to fail (which is extremely rare), the main operation continues — the system never fails due to audit issues.
How to use it?
Access the audit record
Go to Audit in the sidebar. Requires administrator permissions.
Filter the records
The complete record can have thousands of entries. Use filters to find what you need:
| Filter | Example use |
|---|---|
| Resource type | See only changes to agents, or only to tasks, or only to configurations |
| Action | See only creations, or only deletions, or only modifications |
| Actor | See all actions by a specific user |
| Date range | See everything that occurred during a specific period |
| Resource ID | See the complete change history of a specific element |
Read an audit entry
Each entry shows:
- Exact timestamp of when it occurred
- Who did it (user name or indication that it was the automated system)
- What action they performed
- On which element
- The values before and after (for modifications)
View the complete history of an element
To see all the changes a specific element has undergone (for example, an agent's configuration over time):
- Filter by the resource type and the element's ID.
- The results show the complete change timeline.
This allows reconstructing exactly how an element's configuration evolved and identifying when a change was introduced that caused a problem.
Export for external audits
To respond to an external audit:
- Apply the filters for the required period and event type.
- Click Export.
- Download the JSON file with all records from the period.
The exported file includes integrity verification metadata that allows auditors to confirm that the records have not been altered.
Audit export is available on Professional and Enterprise plans and requires system administrator permission.
What actions are recorded
| Category | Recorded actions |
|---|---|
| Agents | Create, modify configuration, activate, deactivate, delete |
| Tasks | Create, change status, reassign, modify priority, close, delete |
| Assets | Create, modify data, change operational status, delete |
| LOTO | Create procedure, submit for review, approve, reject, start execution, complete step, abort |
| Personnel | Add member, modify contact data, change department, delete |
| Rules and configuration | Create, modify, activate, deactivate event rules |
| System users | Create account, change permissions, access to sensitive modules |
| API keys | Create, regenerate, revoke |
Key benefits
- Automatic record of all actions without anyone having to document anything
- Guaranteed immutability — no record can be altered after creation
- Cryptographically verifiable chain to demonstrate record integrity
- Responds to external audits (ISO, OSHA, industry regulations) with exportable data
- Allows investigating incidents: who did what and exactly when
- Reconstruction of any element's state at any point in time
Common use cases
Scenario 1: ISO 9001 audit The quality team receives an ISO 9001 audit. The auditor asks for evidence that changes to the parameters of monitored processes have access control and logging. The quality manager accesses the Audit module, filters by "modifications to agents and data sources" for the audit period, and exports the record. The document shows who changed which configuration, when, and what the previous values were. Audit passed.
Scenario 2: Investigate a security incident A critical alarm in the LOTO system was deactivated without anyone remembering having done it. The safety coordinator opens the Audit, filters by resource type "LOTO" and action "modify" for the week of the incident. They see that the user admin@company.com deactivated the LOTO procedure for compressor C-02 on Tuesday at 2:23 PM. With that information, they can speak with that person to understand what happened.
Scenario 3: Compliance for changes to critical configuration An industry regulation requires that any change to the alarm configurations of safety equipment be documented and traceable. With the audit record, every time someone modifies an alarm threshold on a critical piece of equipment, it is automatically recorded with the previous and new state, the user who did it, and the exact timestamp — with no need for manual change control forms.
Data Management
Retention policies, complete data export for audits or migration, and data deletion when regulatory compliance requires it.
Mobile App
Rela AI works as a phone app without downloading from an app store. It installs in seconds from the browser and works even when internet signal is intermittent.