> 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/projects-and-purpose-based-access-control.md).

# Projects and Purpose-Based Access Control

Projects combine users and data sources under a common purpose, which can then be used to restrict access to data and streamline collaboration.

There are three main use cases Immuta projects can help with:

1. [Allowing policy owners to create exceptions to policies in a proactive manner](#projects-and-purpose-based-access-control)
2. [Allowing users to securely collaborate on data](#equalized-access)
3. [Allowing control over what data can and cannot be joined](#masked-joins)

For any of these use cases, project workspaces can be created to allow users to [write data to the project](#writing-to-projects).

## [Projects and purpose-based access control](/latest/governance/author-policies-for-data-access-control/projects-and-purpose-based-access-control/projects-and-purpose-controls.md)

This section includes conceptual, how-to, and reference guides for using projects to enforce purpose-based access controls on your data.

## [Equalized access](/latest/governance/author-policies-for-data-access-control/projects-and-purpose-based-access-control/equalized-access.md)

This section includes conceptual, how-to, and reference guides that explain how equalized entitlements work in Immuta and how you can use them to effectively collaborate across your department without risk of data leaks.

## [Masked joins](/latest/governance/author-policies-for-data-access-control/projects-and-purpose-based-access-control/masked-joins.md)

This section includes conceptual and how-to guides that explain how to effectively use masked joins for your business use case.

## [Writing to projects](/latest/governance/author-policies-for-data-access-control/projects-and-purpose-based-access-control/writing-to-projects.md)

This section includes conceptual, how-to, and reference guides for writing data to projects and sharing that data with other Immuta users with proper access controls enforced.


---

# 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/projects-and-purpose-based-access-control.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.