> 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/administration/authentication-configuration/manage-projects/manage-project.md).

# Managing Project

## Assigning Project

To assign the project, perform the following actions:

1. On the **Home** page, select **Admin**.
2. On the **Admin** page, select **Project Management**. The **Assigned Projects** tab opens.
3. From the **Username** dropdown, select the username.&#x20;
4. From **All Projects** section, select the project to assign it to specific user.
5. Select **>** arrow. Selected project moves to **Assigned Projects**.

{% hint style="info" %}
**Note:**

* User must be assigned project to access the Project.
* For flexible team configurations based on project needs, any user can be added or removed from required projects.
* These arrows (**>**, **<**) are used to move single project from **All Projects** to **Assigned Project** & vice versa.
* These arrows (**>>**, **<<**) are used to move all the project from **All Projects** to **Assigned Project** & vice versa.
  {% endhint %}

6. Select **Save**.

### Deleting Project

To delete the project, perform the following actions:

1. On the **Home** page, select **Admin**.
2. On the **Admin** page, select **Project Management**. The **Assigned Projects** tab opens.

{% hint style="info" %}
**Note**: Only users with the **Admin** role can delete a project. Users with the **Quality Manager** role cannot delete a project, even if they have **Admin** as their secondary role.
{% endhint %}

3. Select **Delete Project** tab.
4. From the **All Projects** dropdown, select the project.
5. Select **Delete**.


---

# 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/administration/authentication-configuration/manage-projects/manage-project.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.
