> 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/kilo-iot-server/reports.md). # Records & Reports 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](/kilo-iot-server/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](/kilo-iot-server/reports/key-vault.md) — An encrypted store for your devices' EUI-key pairs, so credentials outlive the installer who commissioned the hardware.
The Audit Trail page with its actor filter, event type dropdown and date range control above the event list
## 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kiloiot.io/kilo-iot-server/reports.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.