> 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/review-access-requests/how-to-guides/manage-dynamic-review-flows.md).

# Manage Dynamic Review Flows

Configure, edit, or override dynamic review flows for assets and data products

{% hint style="info" %}
**New feature**

Immuta is gradually rolling out dynamic review flows to accounts. If you do not see this feature in the Request app, contact your Immuta support professional to ask about availability for your account.
{% endhint %}

### Requirements

* To manage dynamic review flows for assets, you must have the `GOVERNANCE` permission.
* To manage dynamic review flows for data products, you must have the `GOVERNANCE` permission or the `Manage Data Products` permission in the data product's domain.

Dynamic review flows are configured separately for each asset or data product and request type. You can configure a separate flow for:

* **Access requests**
* **Masking exceptions**

For information about dynamic review flow concepts and supported decision expressions, see the [Review flows reference guide](https://documentation.immuta.com/saas/request/review-access-requests/reference-guides/review-flows.md).

## Configure the review flow

1. Navigate to the asset or data product.
2. On the **Review flows** tab, use the dropdown to select the **Request type**.
3. Then, click Edit, select a node on the canvas to view, and edit its settings in the side panel.

*The flow starts with a **Request initialized** node. This node does not have configurable settings.*

### Add a request form

A request form is optional. Use a request form when you need to collect information from the data consumer before Immuta evaluates the flow. You can reuse the same request form across multiple flows.

To add a request form,

1. Select the **Request form** node on the canvas.
2. In the settings panel, search for an existing request form.
3. Select the request form from the search results.
4. Review the questions displayed in the request form preview.
5. Continue configuring the decisions and outcomes in the flow.

Answers from the request form can be referenced in decision expressions.

### Add a decision

Decision nodes evaluate an expression and route the request to a **Yes** or **No** branch.

To add a decision,

1. Hover over the node where you want to add the decision.
2. Click the green **New decision** icon.
3. Select the new **Decision** node on the canvas.
4. In the settings panel, [enter the decision logic](#enter-decision-logic).
5. Review the **Yes** and **No** branches created by the decision.
6. Add additional decisions or outcomes to each branch as needed.

#### Enter decision logic

When you select a decision node, the settings panel displays the **Enter decision logic** field. Enter the expression that determines whether the request follows the **Yes** or **No** branch.

The editor provides suggestions for available decision facts and operators. You can select a suggestion to insert it into the expression field, or enter the expression directly.

Current decision facts include the following:

* `@request`: Facts about the request, including whether it is self-service, the requested access duration, and request form answers. *Short answer questions are not supported.*&#x20;
* `@consumer`: Groups, attributes, and Immuta permissions for the person who will receive access if the access request is approved.
* `@requestor`: Groups, attributes, and Immuta permissions for the person who submitted the request.

A user can request access on behalf of another user. In that scenario the requestor and consumer are different people. The following expression evaluates whether the request is for the person submitting it:

```
@request.isSelfRequest == true
```

Use the facts and operators shown in the decision editor and see the [Review flows reference guide](https://documentation.immuta.com/saas/request/review-access-requests/reference-guides/review-flows.md#supported-decision-expression-logic) for additional details about supported expressions and examples.

### Add an outcome

An outcome defines what happens when a request reaches the end of a branch.

To add and configure an outcome,

1. Select the outcome node on the canvas.
2. In the settings panel, open the **Select outcome** dropdown.
3. Select one of the available outcomes:
   * **Automatically approve**:&#x20;
     * Enter a **Justification** explaining why requests that reach this outcome can be approved automatically.
     * Configure the **Duration**:
       * Leave the duration unset if the approval should not have a configured expiration.
       * Enter a duration if access should be temporary.
   * **Automatically deny**:
     * Enter a **Justification** explaining why requests that reach this outcome must be denied.
   * **Human review**:
     * &#x20;Under **Data stewards**, select a source type.
     * Select the value for the source. Depending on the flow, you can select sources such as
       * A specific user
       * A group
       * An attribute
       * A global permission
       * A domain permission
       * A catalog permission
     * Confirm that the source appears in the data steward table.
     * Repeat these steps to add additional data steward sources.
     * Under **For selected stewards, whose approval is required?**, select one of the following:
       * **Any**: A determination from one data steward in the configured sources completes the review.
       * **All**: A determination from each configured data steward source is required.
     * Under **Require temporary approvals only**, select **Yes** or **No**.
       * If you select **Yes**, configure the optional **Maximum allowable duration**.
   * **Review Assist** (Available for access requests):
     * Under **Add data stewards**, select the sources that should review requests when review assist cannot make a determination.
     * Select **Any** or **All** to determine how many of the selected sources must provide a determination.
     * Under **Require temporary approvals only**, select **Yes** or **No**.
       * If you select **Yes**, configure the optional **Maximum allowable duration**.
4. Confirm that the outcome is the final node on the branch.

{% hint style="info" %}
Changes to a dynamic review flow do not reevaluate requests that were already completed. Immuta evaluates the flow when a request is submitted.
{% 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/review-access-requests/how-to-guides/manage-dynamic-review-flows.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.
