> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/latest/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/latest/governance/author-policies-for-data-access-control/authoring-policies-in-secure/section-contents.md).

# Subscription Policies

Learn how to manage table-level access with subscription policies

Subscription policies manage table-level access to data. The how-to and reference guides in this section detail how to implement subscription policies to meet your compliance requirements and describe the types of subscription policies available.

## How-to guides

* [Author a subscription policy](/latest/governance/author-policies-for-data-access-control/authoring-policies-in-secure/section-contents/how-to-guides/subscription-policy-tutorial.md): Author a subscription policy to manage access to data sources.
* [Author an ABAC subscription policy](/latest/governance/author-policies-for-data-access-control/authoring-policies-in-secure/section-contents/how-to-guides/abac-subscription-policy.md): Author a subscription policy that uses attribute-based access controls to automate data access decisions.
* [Subscription policies advanced DSL builder](/latest/governance/author-policies-for-data-access-control/authoring-policies-in-secure/section-contents/how-to-guides/advanced-dsl-policies.md): Author a subscription policy using the advanced special functions.
* [Author a restricted subscription policy](/latest/governance/author-policies-for-data-access-control/authoring-policies-in-secure/section-contents/how-to-guides/restricted-subscription-policies.md): As a data owner, author a single subscription policy that can apply to multiple data sources you own.

## Reference guides

* [Subscription policies reference guide](/latest/governance/author-policies-for-data-access-control/authoring-policies-in-secure/section-contents/reference-guides/subscription-policies.md): This reference guide describes the design and behavior of Immuta subscription policies.
* [Subscription policy access types](/latest/governance/author-policies-for-data-access-control/authoring-policies-in-secure/section-contents/reference-guides/subscription-access-types.md): This reference guide describes read and write access policies and how they translate to privileges in the remote data platform.
* [Advanced DSL policy builder functions and variables](/latest/governance/author-policies-for-data-access-control/authoring-policies-in-secure/section-contents/reference-guides/advanced-special-functions.md): This reference guide defines the advanced functions available when building subscription policies.


---

# 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/latest/governance/author-policies-for-data-access-control/authoring-policies-in-secure/section-contents.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.