# Introduction

The Request app is how you manage request and approve workflows in Immuta to grant data access to your users. Access can refer to a single asset in a catalog (such as databases, schemas, or tables), an entire data product and its objects, or a masking exception to view unmasked data within specific columns.

By replacing ticketing systems and manual grants with automated, self-service workflows, the Request app streamlines data access at both the table- and column-level. This approach reduces operational overhead and accelerates insights while ensuring that governance teams maintain complete visibility, control, and auditability as the data ecosystem grows.

The Request app enables data consumers, stewards, and managers to perform the following actions:

* **Discover and request access**: Data consumers can quickly discover and [request access](/SaaS/request/access-data-products/how-to-guides/requesting-access-from-your-catalog.md) to data within the data catalogs they are already working in.
* **Delegate stewardship**: Organizations can delegate data stewards to [receive requests](/SaaS/request/review-access-requests/how-to-guides/view-and-respond-to-access-requests.md#view-access-requests) for access and [make determinations on requests](/SaaS/request/review-access-requests/how-to-guides/view-and-respond-to-access-requests.md#respond-to-an-access-request), allowing the right people to make access decisions.
* **Automate provisioning**: Approvals have a direct impact on access by either [auto-provisioned](/SaaS/request/configure/reference-guides/understanding-access-provisioning-and-underlying-policies-in-immuta.md) object access in the underlying data platform using powerful access policy management features or managing data policies to automatically unmask specific columns for masking exceptions.
* **Manage data products**: [Data product managers](/SaaS/request/introduction/user-types.md#data-product-managers) can be assigned within your organization to publish and [manage data products](/SaaS/request/configure/how-to-guides/manage-data-products.md) in Immuta.
* **Customize the experience**: Organizations can [personalize the Request app](/SaaS/request/configure/how-to-guides/customize-the-marketplace-branding.md) with the brand's logo and colors to give it a branded look and feel.

## Architecture

The Request app is a separate experience from the existing [Govern app](/SaaS/govern/getting-started-with-secure.md), but some actions to set up the Request app must be completed in the Govern app.

{% columns %}
{% column %}

### Govern app

* Application admins register connections
* Application admins configure catalogs
* Governance users set up domains and users
* Application admins customize the Request app branding
  {% endcolumn %}

{% column %}

### Request app

* Governance users configure request forms and review flows for assets and data products
* Data product managers publish data products
* Data consumers fill out request forms to request access to data
* Data stewards review access requests
  {% endcolumn %}
  {% endcolumns %}

For more details about the requirements to set up the Request app, see the [Prerequisites page](/SaaS/request/configure/reference-guides/marketplace-app-requirements.md).

## Use cases

To decide the best use case for your organization, see the [Use cases guide](/SaaS/request/introduction/use-cases.md). Or jump right in and start the [Walkthrough](/SaaS/request/introduction/walkthrough.md) for setting up the Request app with your assets, the recommended use case.


---

# 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/SaaS/request/introduction.md?ask=<question>
```

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.