> 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/govern/secure-your-data.md).

# Author Policies for Data Access Control

Learn how Immuta enforces access controls for your users

Immuta allows you to secure your data through various access control policies you configure.

## [Introduction](/saas/govern/secure-your-data/secure-introduction.md)

This section provides a conceptual overview of Immuta policies and their benefits.

## [Policies](/saas/govern/secure-your-data/authoring-policies-in-secure.md)

This section provides how-to and reference guides for authoring policies to enforce data access controls.

## [Intents](/saas/govern/secure-your-data/intents.md)

This section provides how-to and reference guides for using intents to enforce access control. Instead of basing access decisions solely on who users are, intents allow the policy decision to be based on what the users are doing and why they need access.

## [Projects and purpose-based access control](/saas/govern/secure-your-data/projects-and-purpose-based-access-control.md)

This section provides how-to and reference guides for projects, which combine users and data sources under a common purpose that can then be used to restrict access to data and streamline collaboration.

## [Data consumers](/saas/govern/secure-your-data/data-consumers.md)

The how-to guides in this section illustrate how to subscribe to data sources in Immuta, run health jobs, and complete other actions as a data source subscriber.


---

# 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/govern/secure-your-data.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.