> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/operate/tenant-admin/governance.md).

# Manage access

Grant developers access to Compute and data sources, onboard users, and set up the ApplicationUser and runAsUser mechanics.

Your governance work is the day-to-day grant management that lets a team build safely: who can use which Compute and data source, who is in the Tenant, and how deployed products run under a stable identity. The mechanics are in the [Access control](https://v2.dataos.info/operate/access-control/roles-and-permissions.md); this page is what you do with them.

## Onboard users and assign roles

Use the **Tenant Admin** application to find users in the Instance and assign Tenant roles (Data Developer, Data Consumer, Data Admin). This lets you onboard people without an Operator handling each request.

1. Open the **Tenant Admin** application.
2. Find the user in the Instance (they must be able to sign in to the Instance first).
3. Assign the Tenant role that fits their responsibility.

Guidelines:

* Assign the narrowest role that fits.
* Keep role design consistent with the Operator's conventions so access is predictable.

For role definitions and the capability matrix, see [Roles & Permissions](https://v2.dataos.info/operate/access-control/roles-and-permissions.md).

## Grant someone access

This is the grant you will issue most. By default a developer holds no access to Compute, Depots, Minerva, or Secrets; each needs an explicit `Can Use` grant before it can be referenced in a Data Product workload.

A grant can target an **individual user** or a **Tenant Role**, so you can give one person access or cover everyone who holds a Role in a single grant. To let a developer build on a shared Compute or data source:

1. Open the resource's **Access** tab in the Resource Catalog.
2. Choose the target: the individual developer, or the Tenant Role they belong to.
3. Grant **Can Use**.

The three grant levels:

* `Can Use`: reference a resource in a Data Product workload.
* `Can Edit`: change the resource.
* `Can Manage Access`: grant it onward to others.

### Grant to a Role

Granting to a Role gives the permission to everyone who holds that Role on that Resource. Anyone who joins the Role inherits the access, and anyone removed from it loses the access, without a separate grant or revoke on the Resource.

To grant to a Role:

1. Open the **Resource Catalog** and search for the Resource by name.
2. Open the Resource and go to the **Access** tab.
3. Click **Grant Permissions**.
4. Under **Grant to**, choose **Roles**.
5. Select the Tenant Role.
6. Choose the permission and click **Grant**.

The steps are the same as granting to an individual user; only the **Grant to** choice differs. For a worked example that grants every dependency a Data Product needs, see [How to provide access?](https://v2.dataos.info/operate/recipes/how-to-give-access.md). To check what a Tenant Role already holds before you grant to it, see [Roles & Permissions](https://v2.dataos.info/operate/access-control/roles-and-permissions.md).

Prefer a Role where the access is standard for that Role, such as every Data Developer using the same shared Compute. Reserve individual grants for one-off access, and review those periodically.

## Revoke access

When access is no longer needed (a project ends, a person moves teams, or a product is retired), revoke the grant from the same **Access** tab. Revoking `Can Use` stops new Data Product workloads from referencing the resource; Data Product workloads already running should be migrated or stopped as part of the change.

## Governance practices

* **Grant to roles, review individuals.** Standard access goes to a role; one-off grants to individuals should be reviewed periodically.
* **Track ApplicationUser grants.** They let resources act as another identity; know which exist and revoke when a product is retired.
* **Act on orphaned resources.** When a creator leaves, use your elevated privilege to reassign or clean up their resources so operations stay stable.


---

# 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://v2.dataos.info/operate/tenant-admin/governance.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.
