> 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/features-in-test-case-section-1/assign.md).
# Assigning Test Case
The Assign Test Cases feature helps you assign test cases to the appropriate users or roles within a project. Assigning test cases makes it easier to organize testing activities, define ownership, and ensure that the right users work on the assigned test cases. This article explains how to assign test cases to users.
{% hint style="info" %}
**Note**:
* The **Assign Test Cases** feature is available only to users with the **Quality Manager** with **Admin** as a role in the project.
* Follow the same procedure for other supported modules, such as **Element Repository**, **Execution List**, **Data Table**, and **Reusable Library**.
{% endhint %}
To assign test cases, perform the following actions:
1. On the **Home** page, under **Projects**, select the required project.
2. Go to **Design Studio** > **Test Case**.
3. Select the required folder.
4. Select the **See more** (**...**) icon, select **Assign test cases**. The **Test Case Assignment** dialog opens.
5. Select the required user from the **Assign** drop-down list for each test case.
{% hint style="info" %}
**Note:** You can search for users who are part of the project in the **Assign** list.
{% endhint %}
6. Select **Assign**.
{% hint style="info" %}
**Note**: Use the **Search Test Case** box to search for a specific test case within the selected folder.
{% endhint %}
---
# 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-test-case-section/features-in-test-case-section-1/assign.md?ask=&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.