> 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/governance-enforced.md).

# Governance enforced on you

Why you see what you see, and how to ask for more.

As a Consumer, governance mostly works behind the scenes. You do not configure policies, but they shape what you can see in a Data Product. Understanding this helps you read results correctly when data appears masked, filtered, or unavailable.

## What is enforced

The Data Product owner defines the access policies for the product. When you query the product, DataOS checks those policies against your identity and applies the governed result across every supported path, such as SQL, REST, GraphQL, and product interfaces.

These policies can shape what you see in two main ways:

**Masked columns:** Sensitive fields, such as email addresses, customer names, identifiers, or signup dates, may be protected by a masking policy. When the policy applies to you, the field still appears in the result, but the raw value is replaced with a protected value, such as `null`, a hash, or another masked expression.

**Row-level filters:** Some results may be narrowed by row-level policies. For example, a Data Product may include data across regions, business units, customer segments, or statuses, but the policy that applies to you may show only the slice you are allowed to query, such as your assigned region or business unit.

This is deny-by-default behavior working as designed. You see only what you have been granted, and protected data does not leak by accident. See the [Access control](https://v2.dataos.info/operate/access-control/roles-and-permissions.md) to know more.

## Read results with this in mind

* A masked or empty column is usually a policy, not a data-quality problem. Check before you raise it as a bug.
* A total that seems low may be a row filter scoping you to a subset. Confirm what slice you are entitled to.

## Ask for more

If you have confirmed it is a policy and you still need the data, the product owner decides. Find them in the **Contacts** section of the product's page in the Data Product Hub, and tell them which field or which rows you need and why you need them. If they agree, the change reaches you as an audited grant or a policy update, not as a change to the data itself.

See [Raise issues and track changes](https://v2.dataos.info/operate/data-consumer/support-and-changes.md) for how to reach an owner and what to include.


---

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