> For the complete documentation index, see [llms.txt](https://bluurdoc.bluur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluurdoc.bluur.ai/en/getting-started/quick-start/key-features/event-log-and-auditability.md). # Event log and auditability The system logs activities related to documents, projects, user accounts, and organization configuration. [**Anonymization history**](/en/functions/event-log/anonymization-history.md) allows you to check, among other things: * the document name and status, * the anonymization execution date, * the user performing the operation, * the project and assigned team, * the number of pages, * processing time, * the history of subsequent operations. [**System events**](/en/functions/event-log/system-events.md) cover a broader range of activities, including logins, opening documents, actions on projects, tag changes, and operations performed by users and the system. The logs support internal control, incident analysis, accountability of user actions, and reconstruction of the document lifecycle from its addition to anonymization, archiving, or deletion. --- # 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://bluurdoc.bluur.ai/en/getting-started/quick-start/key-features/event-log-and-auditability.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.