> 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/v1/data-consumer/get-access.md).

# Get access

By default, a Data Consumer does not get access to every Data Product. To consume a Data Product, you need access to the Tenant where it is published and access to the specific Data Product you want to use, because Data Products are governed separately.

## Request Tenant access

* **Tenant access.** If you're not in the Tenant yet, your [Tenant Admin](/operate/v1/tenant-admin/tenant-admin.md) invites you and gives you the `Data Consumer` role.

Default Tenant access for the Data Consumer role lets you sign in and use Tenant's UI applications, such as the Data Product Hub and lets you search and browse products in the Hub.

{% hint style="info" %}
However, Tenant access does not determine which Data Products you can use. Product access is governed separately by each Data Product’s own access rules.
{% endhint %}

## Request Data Product access

The **Data Consumer** role does not give you access to every Data Product automatically. For each product you want to use, request access through the appropriate channel from the product owner or your Tenant Admin. You can usually find the owner in the product’s **Contact** section in the Data Product Hub.

Approved product access gives you read-only access to that Data Product. What you can see and query may still be shaped by the product’s governance, such as masking or row filters.

## What read-only access means

As a Data Product Consumer, you can find, evaluate, and query the Data Products you are granted, and use Consumer applications to explore them.

You cannot create resources, run Data Product workloads, edit Data Products, or manage access.

## Get API Token

After you have Tenant and Data Product access, you may need a DataOS API token to connect external tools such as Power BI, Tableau, SQL clients, APIs, or AI clients.

The API token identifies requests from the external tool as coming from your DataOS user account. DataOS then applies your existing access, including product permissions, masking, and row filters, to decide what the tool can query and return. See [API tokens](https://v2.dataos.info/references/key-concepts/api-tokens) in References for more on how tokens work.

Unlike the `Data Developer` and `Data Admin` roles, `Data Consumer` doesn't include `metis-resource-tabs-access`, so you won't see the metadata, lineage, and schema tabs on the Tenant's Resource Catalog. Your view is limited to the Data Product Hub.

## Elevate access

If you need to build on a product (transform it, join it, or publish something new), that's Developer work: request the `Data Developer` role and follow [Get access and readiness](/operate/v1/data-developer/access-and-readiness.md) in the Developer section.

If a product shows masked columns or fewer rows than you expect, that's governance working as intended, not a bug. To ask for broader access, contact the product owner and explain what you need and why; see [Governance enforced on you](/operate/v1/data-consumer/governance-enforced.md). Once you have access, [Consume](https://v2.dataos.info/consume) covers how to use the product.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/operate/v1/data-consumer/get-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.