> 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-test-case-section/e2e-flow-end-to-end-flow/viewing-e2e-flow-details-and-audit-logs.md).

# Viewing E2E Flow Details and Audit Logs

The E2E Flow details help you understand the key information related to E2E Flow. You can view details such as the E2E Flow name, description, status, creation date, time, and the user who created it. 

The E2E Flow audit logs track the history of changes made to E2E Flow folder or E2E Flow. Use this article to understand how to view E2E Flow details and audit logs.

## Viewing E2E Flow Details

To view E2E Flow Details, perform the following actions:

1. On the **Home** page, from **Projects** list, select required project.
2. Select **Design Studio**.
3. Select **Test Case**.
4. On the **Test Case** page, expand the **E2E Flows** and select the E2E Flow for which you want to see the details.
5. Select the **Information Panel** (**i**) icon. The **Details** tab opens.
6. On the **Details** tab, you can view the following information:

* **E2E Flow Name**: The E2E Flow name.
* **Description**: The E2E Flow description.
* **Status**: The E2E Flow [status](/avo-assure/create-and-execute-tests-with-design-studio/test-artifacts-in-avo-assure.md#understanding-different-statuses-of-test-artifacts) (New, In Progress, Under Review, Approved or Rejected).
* **Created On**: The E2E Flow creation date and time.
* **Created By**: The username of the person who created the E2E Flow.

## Viewing E2E Flow Audit Logs

To view E2E Flow Audit Logs, perform the following actions:

1. On the **Home** page, from **Projects** list, select required project.
2. Select **Design Studio**.
3. Select **Test Case**.
4. On the **Test Case** page, expand the **E2E Flow** and select the E2E Flow for which you want to see the details.
5. Select the **Information Panel** (**i**) icon. The **Details** tab opens.
6. Select the **Audit Logs** tab.
7. Select **Date Range** to view the actions performed between the specified dates.
8. Expand the month to view the actions performed in the E2E flow.

### E2E Flow Audit Log Inclusions

The following actions are captured in the E2E Flow audit logs:

* Performing Folder Level Actions
* Creating E2E Flow Folder
* Renaming E2E Flow Folder
* Creating E2E Flow
* Renaming E2E Flow
* Adding Test Case to E2E Flow
* Deleting Test Case from E2E Flow

### E2E Flow Audit Log Exclusions

The following actions are currently not captured in the E2E Flow audit logs:

* Reordering E2E Flow

 


---

# 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-test-case-section/e2e-flow-end-to-end-flow/viewing-e2e-flow-details-and-audit-logs.md?ask=<question>&goal=<endgoal>
```

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