> 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/functions/event-log.md). # Event log Section **Event log** presents information about the history of working with documents and activities performed in the Bluur® system. The user will find here a description [**Anonymization history**,](/en/functions/event-log/anonymization-history.md) which allows you to check the most important information about processed documents, including the anonymization date, document status, the person performing the operation, the number of pages, processing time, and a detailed history of actions. The section also includes [**System events**](/en/functions/event-log/system-events.md), in which operations performed by users and the system are recorded, such as opening documents, changes in projects, adding and removing tags, logins, and other activities related to account and document management. Thanks to the event log, administrators and users with appropriate permissions can monitor workflow, check who performed a given operation and when, and track the document life cycle from the moment it is added all the way 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/functions/event-log.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.