> For the complete documentation index, see [llms.txt](https://docs.qubitro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qubitro.com/add-ons/audit-log.md). # Audit Log The Audit Log provides a detailed record of actions performed within your Qubitro account. ### Overview The **Audit Log** provides a detailed record of actions performed within your Qubitro account, helping you track changes, monitor activities, and maintain compliance. ### Core Features * **Enterprise-Only Feature** – Available for Enterprise plan users. * **Event Tracking** – Logs key actions such as project modifications, device updates, user access changes, and function executions. * **Historical Visibility** – Provides a timeline of events for improved accountability. * **Security & Compliance** – Helps organizations meet audit and compliance requirements. {% hint style="warning" %} Audit Log is an **upcoming feature** and will be available under **Organization Settings** for Enterprise accounts. {% endhint %} ### Need early access to Audit Log? [Contact us](https://www.qubitro.com/contact/sales) to discuss your requirements and enable this feature for your Enterprise account. --- # 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.qubitro.com/add-ons/audit-log.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.