> 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/data-consumer/data-product-consumer.md).

# Overview

{% hint style="info" %}
This section covers operational responsibilities of the Data Consumer role; step-by-step workflows for discovering, evaluating, and using Data Products are covered in [Consume](https://v2.dataos.info/consume).
{% endhint %}

A Data Product Consumer works with approved Data Products and governed outputs. In a Tenant, this maps to the Data Consumer role: read-only access to permitted Data Products and the applications used to explore and consume them.

This role is focused on using trusted data, understanding the controls applied to it, and raising issues when access, quality, freshness, or product behavior needs attention.

## What you do

As a Data Product Consumer, your work begins with access and continues through responsible use of the products available to you.

* [Request the right access](/operate/data-consumer/get-access.md): get access to the Tenant and the Data Products required for your work.
* [Choose a consumption path](/operate/data-consumer/modes-of-consumption.md): consume the product through the path that fits your work, such as a BI tool, query interface, API, or application.
* [Work within governed access](/operate/data-consumer/governance-enforced.md): understand how masking, row filters, and access limits shape what you can see and use, and request to elevate the access when needed.
* [Trust and Freshness](/operate/data-consumer/trust-and-monitor.md): review quality, freshness, ai-readiness, lineage, and activity signals before relying on a product for reporting or decisions.
* [Raise issues and follow changes](/operate/data-consumer/support-and-changes.md): contact the product owner when something looks wrong, and stay aware of changes that may affect your work.

## What you cannot do

* **Build or change products.** Creating resources, running workloads, and editing products is Developer work. As a Consumer, you only read what is published.
* **Grant or manage access.** You cannot grant access to a product or resource, even one you requested. The product owner or a Tenant Admin makes that decision.
* **Browse Tenant resources.** The metadata, lineage, and schema tabs that Developers and Admins use are not available to you. You find products in the Data Product Hub, not the Resource Catalog.

## Start with

Start with [Request access](/operate/data-consumer/get-access.md) to understand what your Tenant role allows and which product-level grants you need.


---

# 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/data-consumer/data-product-consumer.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.