> For the complete documentation index, see [llms.txt](https://support-en.braver.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support-en.braver.net/for-administrators/audit-logs.md). # Audit Logs ## What are audit logs? As healthcare organizations, you may be required to keep a record of all important activities of your organization's members regarding their access to patient health data. Braver automatically collects read accesses performed by members of the organization to all information for which your organization is the custodian. Braver also automatically collects actions of creation and modification of information, as well as any communication actions performed on the platform. {% hint style="success" %} For a complete list of items captured in the audit logs, refer to the page [What can I find in the audit log](/for-administrators/audit-logs/what-can-i-find-in-the-audit-log.md). {% endhint %} ### What constitutes an audit log entry? Audit logs do not store the *content* of the action performed (e.g., the specific details of a patient consulted). They only store metadata about the action, dates, and references: * The type of action: *Creation, modification, deletion, etc.* * The type of entity: *Patient, Discussion thread, Care channel, etc.* * The identifier of the actor (the user or service account in the case of automations) * The identifier of the entity subject to the action (e.g., the patient consulted, the discussion thread created, etc.) * The date and time when the action was performed ### How long are these logs retained? Currently, logs are retained indefinitely and can never be deleted. In the future, you will be able to specify a retention period for these logs. --- # 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://support-en.braver.net/for-administrators/audit-logs.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.