> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-element-repository-section/features-in-element-repository/element-identifier-order-1/reorder-element-and-element-properties-in-repository.md).
# Viewing Element Repository Audit Logs
## Viewing Element Repository Audit Logs
To view the Element Repository **Audit Logs**, perform the following actions:
1. On the **Home** page, from **Projects** list, select the required project.
2. Select **Design Studio**.
3. On the **Element Repository** page, expand required folder and select the element repository for which you want to see the Audit Logs.
4. Select the **Open information** (**i**) icon. The **Details** tab opens.
5. Select the **Audit Logs** tab.
6. Select **Date Range** to view the actions performed between the specified dates.
7. Expand the month to view the actions performed in the element repository.
### Audit Log Inclusions
The following actions are captured in the element repository audit logs:
* Creating or Moving Folders within Element Repository
* Creating an Element Repository
* Renaming the Element Repository
* Adding or Removing Self Heal Configurations
* Assigning Element Repository
* Requesting Review and the Status of Review
* Creating or Capturing Elements
* Mapping Elements
* Renaming Elements
* Deleting Elements
* Importing Elements
* Modifying Element Properties
* Copying and Pasting Elements
### Audit Log Exclusions
The following actions are currently not captured in the element repository audit logs:
* Deleting Repository
* Exporting Elements
* Reordering via Element Identifier
* Comparing Elements
* Replacing Elements
* Cutting Elements
---
# 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://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-element-repository-section/features-in-element-repository/element-identifier-order-1/reorder-element-and-element-properties-in-repository.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.