Appearance
Audit trails
What is this?
Dataplicity history records supported access and operational events with the actor, device or organisation, action, and time fields available for that event type.
Why does it matter after devices ship?
Remote access to customer-deployed devices is sensitive. Security review and incident investigation need evidence of supported platform access and actions, correlated with device-side and external records where the complete response spans more than Dataplicity.
How does it work in Dataplicity?
Review the event surfaces available to your organisation. Coverage, fields, retention, and export options depend on the action and organisation configuration. A platform event does not necessarily record every device-side effect of a command or an action taken outside Dataplicity.
When should I use it?
- Customer contracts require access records - verify Dataplicity's supported event coverage, retention, and export options against the specific requirement before relying on them
- Security review needs evidence of controlled remote access
- An incident investigation needs to correlate platform access with device and service evidence
- Your control framework requires individual accountability and retained operational records
Example workflow
During an incident review, an administrator opens the organisation or device event history and correlates access events with the affected device and time window. Dataplicity shows the retention and export options available to your organisation.