> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/reports.md).
# Records & Reports
Records & Reports in Kilo IoT — the Audit Trail of membership activity and the encrypted Key Vault for device keys.
The Records & Reports section holds the two places your organization keeps things on the record: a log of who did what, and an encrypted store for the credentials your devices depend on.
* [Audit Trail](/reports/audit-trail.md) — A searchable log of all membership and access events: invitations sent, users joining, permission changes, and user removals. Filter by actor, event type, and date range.
* [Key Vault](/reports/key-vault.md) — An encrypted store for your devices' EUI-key pairs, so credentials outlive the installer who commissioned the hardware.
## Audit Trail
Access is controlled by the Audit Trail permission — only users with explicit access can view these records.
## Key Vault
Radio credentials are hard to recover once they leave the box. A LoRaWAN device needs its DevEUI and AppKey; a MIOTY endpoint needs its EP EUI and Network Key — and whether the secret half can be read back off a unit depends on the manufacturer, often needs a wired connection, and is never practical once the hardware is installed. Key Vault keeps those pairs encrypted at the organization level, searchable by partial EUI or key, and reachable when a replacement unit needs provisioning years after commissioning. Access is governed by its own Key Vault permission, granted separately from every other page.
Both pages are reached from the sidebar under **Records & Reports**.
---
# 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.kiloiot.io/reports.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.
