> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/saas/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/saas/request/configure/how-to-guides/manage-assets.md).

# Manage Assets

Attach a request form to or configure a review flow for an asset

Assets are populated from connections. Currently the only editable options are to change the attached request forms and review flow.

## Attach a request form to an asset

Overriding the access or masking exception request form at any level of the hierarchy will result in all children of that asset now inheriting the new request form, unless a child also has overridden the request form.

1. From the <i class="fa-cubes">:cubes:</i> [**Assets** page](https://app.immutacloud.com/marketplace/assets), select the asset you want to update.
2. Click **Edit** for the access or masking exception request form you want to change.
3. Select **Override**. This specific asset you are editing will no longer inherit the request form of the asset containing it and will now have its own request form.
4. Use the dropdown to select the new request form to use.
5. Click **Save**.

## Configure a review flow to an asset

Configuring review flows at the asset level is only possible if the assigned request form delegates the review flow. If it does not, the review flow configured at the asset level will be **Inactive**. You must change the request form to **Delegate** in order to change this behavior.

{% hint style="warning" %}
Changing the request form to delegate means that all assets where it is being used will use the review flow specified at the asset level. If you have not configured the review flow at the asset levels, it defaults to requiring a data steward with the `GOVERNANCE` permission.
{% endhint %}

1. From the <i class="fa-cubes">:cubes:</i> [**Assets** page](https://app.immutacloud.com/marketplace/assets), select the asset you want to update.
2. Go to the **Review flows** tab.
3. Confirm the Review flow you intend to update is not **Inactive**.
4. Click **Edit** to update the access request or masking exception request active review flow you want to change.
5. Select **Override**.
6. Configure the review flow.
7. Click **Save**.

{% hint style="info" %}
If stewards are assigned at the request form level, they **can** edit that request form. If stewards are assigned at the asset (or data product) level, they **cannot** edit that request form.
{% 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://documentation.immuta.com/saas/request/configure/how-to-guides/manage-assets.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.