> 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/governance-enforced.md). # Governance enforced on you 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](/operate/v1/access-model.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 When you consume a governed Data Product, interpret the result with access policies in mind. A masked or empty value is often a policy outcome, not a data-quality issue. Check whether the field is intentionally protected before raising it as a bug. --- # 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/governance-enforced.md?ask=&goal= ``` `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.