> 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/readme.md). # Immuta Documentation - SaaS Use Immuta to provision governed access to data. Apply policy-driven controls and automated workflows to deliver secure, consistent access for users and AI agents. ## Configure Immuta
1 - Connect your data platformBefore you can create policies or share data products, Immuta must be connected to your data platform to manage controls and grant access.Connect your data platform@2x.jpgConnect Integrations
2 - Add metadata and usersFor automated policies, tag data and use those tags in policy. Tag your data by connecting Immuta to data catalogs you already use or run identification.Manage data metadata and add users@2x.jpgManage Data Metadata
3 - Organize data into domainsJust like your organization compartmentalizes ownership of data to different teams and within different platforms, your data in Immuta should be organized into domains.Organize data into domains@2x.jpgOrganize Data into Domains
## Explore Immuta
Request appThe Immuta request app offers a solution for request and approve workflows. Use the data marketplace to share data products, or configure it with your data catalog to receive and manage data access requests.Introduction
Govern appThe Immuta govern app offers a data governance solution for multi-platform architectures. Use policies to manage access control on your data with comprehensive audit on actions within Immuta and queries on your data.Use Cases
ConfigurationConnect your data, metadata, and users.Connect Integrations
Developer guidesInteract with Immuta through the Immuta CLI and API.API Guides
--- # 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 dynamically 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/readme.md?ask=&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 `build a script that syncs our docs to a CMS` 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.