> 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.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Ft5X75hipKqMjNoSdOMnn%2Funknown.png?alt=media&amp;token=eb474674-ad75-41c4-afc9-134e6a961f57" alt=""><figcaption></figcaption></figure>

5. Select the **Audit Logs** tab.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F97xCrZYvxJXqger7UXCI%2Funknown.png?alt=media&amp;token=196dfdfc-e837-4ad1-b7e6-124ca6ed842d" alt=""><figcaption></figcaption></figure>

6. Select **Date Range** to view the actions performed between the specified dates.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FYH8tD8pJ5TIMKBfqqVmF%2Funknown.png?alt=media&amp;token=a6b3167c-bf33-48f7-a1e2-855cfc04066c" alt=""><figcaption></figcaption></figure>

7. Expand the month to view the actions performed in the element repository.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FYC8HtsOcHDuFolAxw1wA%2Funknown.png?alt=media&amp;token=81a9c589-9cd0-440d-8595-3f62b0c01687" alt=""><figcaption></figcaption></figure>

### 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
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=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
