# Create and Manage Purposes
**Requirement**: `GOVERNANCE` or `PROJECT_MANAGEMENT` Immuta permission
## Create a purpose
1. Click the :shield: **Policies** icon in the navigation menu and select **Purposes**.
2. Click **+ Add Purpose**.
3. Complete the **Purpose Name** field, and opt to customize the acknowledgement statement or add a description.
4. Click **Create**.
## Create sub-purposes
1. Click the :shield: **Policies** icon in the navigation menu and select **Purposes**.
2. Open the dropdown menu and click **View or Edit** in the actions column of the purpose you want to add sub-purposes to.
3. Click **Add Sub-Purposes**.
4. Enter a name in the **Enter nested purpose** field in the **Sub-Purpose Builder**.
5. Click the **arrow** to the right of the purpose or sub-purpose(s) to continue adding nested purpose fields.
6. Click **Save**.
A list of sub-purposes will populate at the bottom of the page. You can manage these sub-purposes by clicking **Edit** in the **Actions** column at any time.
## Add a purpose to an existing project
1. Click :database: **Data** in the navigation menu and select **Projects**.
2. Go to the project overview page and click **Add Purposes**.
3. Select the purpose from the dropdown menu or click **Create Purpose**.
4. Complete the prompts in the modal and then click **Save**.
For the purpose to go into effect, it must be approved by a user with the `GOVERNANCE` or `PROJECT_MANAGEMENT` Immuta permission.
## Customize acknowledgement statements
1. Click the :shield: **Policies** icon in the navigation menu and select **Purposes**.
2. Open the dropdown menu and click **Edit** in the **Actions** column of the purpose you would like to customize.
3. Click **Edit** above the acknowledgement statement, customize the text, and then click **Confirm**.
The page displays the updated statement, which now will be used by all projects and purposes. The updated statement will also be used by any new members joining existing projects containing purposes with default statements.
By default, sub-purposes will inherit the acknowledgement statements of their parent purposes. However, you can customize the acknowledgement statement for an individual sub-purpose as well by following the process above.
## Manage purpose requests
1. Navigate to your user profile page and click the **Requests** tab.
2. **Approve** or **deny** the purpose request in the actions column.
## Delete a purpose
1. Click the :shield: **Policies** icon in the navigation menu and select **Purposes**.
2. Click the **more actions** icon in the **Actions** column of the purpose or sub-purpose you want to delete.
3. Select **Delete**, and then click **Confirm** to approve the deletion.
Any project that contained the deleted purpose will be treated as no longer compliant, so the project overview page will display a `violation` tag. Project owners can remediate the violation by [removing the purpose](https://documentation.immuta.com/latest/governance/author-policies-for-data-access-control/projects-and-purpose-based-access-control/projects-and-purpose-controls/project-management/manage-projects#remove-a-purpose-from-a-project) from the project.
---
# Agent Instructions: 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:
```
GET https://documentation.immuta.com/latest/governance/author-policies-for-data-access-control/projects-and-purpose-based-access-control/projects-and-purpose-controls/how-to-guides/purposes-tutorial.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.