> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/foodcore-sensors/technical/audit-trail.md).
# Audit Trail
### Overview
The **Audit Trail** feature in the sensor management platform is a system-level traceability tool designed to maintain transparency and accountability across all administrative activities. It provides a clear, timestamped log of key actions taken on sensors or devices, allowing administrators and compliance teams to review changes, identify who made them, and understand the specific technical alterations involved.
***
### Key Functions
#### 1. **Action Logging**
Each entry in the audit log captures the following information:
* **Time**: The exact date and time the action was performed.
* **User**: The name and email address of the person who initiated the action.
* **Action Type**: The nature of the action taken (e.g., `attachToDashboard`, `downlink`, `upsert`).
* **Raw Data (Optional)**: A technical representation of the action, useful for debugging or forensic analysis.
#### 2. **Traceability by Sensor or Device**
The system logs actions on a per-device basis. This means you can trace all relevant administrative interactions for a specific device, which is particularly useful for investigations, audits, and verifying configurations.
***
### Raw Data Panel
An optional **Raw Data** toggle reveals a JSON-formatted payload for each action. This raw view shows:
* Field-level changes (e.g., `upperThreshold`, `delay`, `label` values)
* Specific settings applied through a `downlink`
* Configuration context when attaching devices to dashboards
#### Example:
```json
{
"label": "Drawer Chiller - Local MZP",
"alerts": [
{
"capability": "temperatureC_SHT",
"upperThreshold": 8,
"upperCompliance": 4
}
]
}
```
This provides clarity on what values were input or modified, and supports technical tracebacks if needed.
***
### Use Cases
* **Change Tracking**: Identify who made specific adjustments and when.
* **Compliance Verification**: Ensure changes are aligned with food safety or operational protocols.
* **Issue Resolution**: Use raw data to diagnose configuration issues or troubleshoot sensor behavior.
***
### Benefits
* Supports **auditability** and **compliance** requirements
* Improves **team accountability**
* Enables **historical traceability** for all critical device interactions
***
### Summary
The **Audit Trail** is a crucial administrative tool for maintaining operational integrity. It not only logs what changes have occurred, but also provides visibility into the context, purpose, and users behind each action. Combined with its technical depth via the raw data option, it ensures a full audit capability for high-stakes environments such as food safety monitoring systems.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.didge.io/home/foodcore-sensors/technical/audit-trail.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
