> For the complete documentation index, see [llms.txt](https://docs.chirpwireless.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chirpwireless.io/reports.md). # Records & Reports Track who has access to your Chirp home, and keep your sensors' join codes safe in an encrypted vault. Two things worth keeping a proper record of: who has access to your household, and the codes your sensors need to get onto your network. * [Activity Log](/reports/audit-trail.md) — A record of all membership events: invitations, joins, permission changes, and removals. Filter by person, event type, or date range. * [Key Vault](/reports/key-vault.md) — An encrypted home for your sensors' DevEUI and AppKey pairs. The activity log is found in the sidebar under **Reports > Audit Trail**. Only household members with the Audit Trail permission can view it. **Key Vault** sits alongside it in the sidebar under **Records & Reports**. Every LoRaWAN sensor ships with a DevEUI and an AppKey — usually on a sticker that stops being easy to reach the moment the sensor goes on the wall. Save the pair to the vault and you can get it back whenever a sensor needs re-adding after a reset, a move, or a swap. It's encrypted, it belongs to your home rather than to one person, and it has its own permission, so you decide who can open it. See [Key Vault](/reports/key-vault.md). --- # 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.chirpwireless.io/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.