> 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/anonymization-history.md).
# Anonymization history
Tab **Anonymization history** contains information about documents that have been processed in the system.
The list shows basic information about the documents:
* **anonymization date**;
* **document name**;
* **document status**;
* **anonymized by** – the user who performed the anonymization.
To display document details, click the arrow icon next to the selected entry. After expanding the entry, the system will show information about the document and the course of its processing.
Expandable anonymization history details.
### Document details
After expanding the entry, the user can check, among other things:
* the project in which the document is located,
* the team responsible for the document,
* the number of pages,
* the document processing time,
* file size,
* creation date,
* file type,
* tags assigned to the document,
{% hint style="info" %}
Processing time determines the period from adding the document to the system to performing its anonymization. The value is presented in hours, minutes, and seconds.
{% endhint %}
### Document operation history
In the panel **Operation history document** presents the chronological sequence of actions performed on the selected document.
* **Document creation**\
The system shows who added the document and when it was created in the system.
* **Document classification**\
The system shows the date and time the classification was performed.
* **Document anonymization**\
The system shows who performed the anonymization and when the document was anonymized.
* **Document opening**\
The system shows who opened the document and when it was opened. In the operation history, openings are grouped into five-minute sessions, so repeatedly opening the same document in a short time does not create separate, repeated entries. Each opening of the document is also recorded in [**System events.**](/en/functions/event-log/system-events.md)
* **Document archiving**\
The system shows who archived the document and when the operation was performed. Archiving removes the source document and leaves only its anonymized version in the system.
* **Document deletion**\
The system shows who deleted the document and when the operation was performed.
This way the user can verify the full document workflow path and check what operations were performed in the system.
Document operation history.
### Downloading a document
From the anonymization history, the document can be downloaded if the download option is available for the given entry.
The owner of the document is the user who added the file to the system. Only that person can download the document from the anonymization history. Other users assigned to the project can see the entry, but do not have access to download the file.
### Document filtering
The date visible on the main list indicates the date of anonymization. The filter **Document added date** refers, however, to the moment the file was uploaded to the system. These are two different stages of document processing.
Filtering makes it possible to narrow the list and find documents meeting specified criteria.
To open the filter panel, click the funnel icon above the document list.
Documents can be filtered by:
* document added date;
* number of pages;
* file size;
* project;
* file type.
After setting the criteria, click the **Apply filters**. To remove the selected criteria and display the full list again, click **Reset filters**.
If no document meets the applied criteria, the list will remain empty. In that case, change the selected values or use the option **Reset filters**.
Document filtering panel in anonymization history.
---
# 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/anonymization-history.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.