> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/SaaS/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/SaaS/configuration/integrations/teradata/reference-guides/accessing-data.md).
# Accessing Data in Teradata
Learn how end users can access policy-enforced data in Teradata
Once data is registered through the Teradata connection, you will access your data through your Teradata client as you normally would. If you are subscribed to the data source, Immuta grants you access to the data in Teradata.
When you submit a query, the Teradata client submits the SQL query to the Teradata server, which then processes the query and determines what data your role is allowed to see. Then, the Teradata server queries the database and returns the query results to the Teradata client, which then returns policy-enforced data to you.
The diagram below illustrates how Immuta, the Teradata server, and Teradata client interact to access data.
## Querying data
Because subscription policies are managed through roles, you must be acting under the role Immuta creates for you to get access to your subscribed data sources.
When querying data in Teradata, use [`SET ROLE ALL`](https://docs.teradata.com/r/Enterprise_IntelliFlex_VMware/SQL-Data-Definition-Language-Syntax-and-Examples/User-Profile-and-Role-Statements/SET-ROLE), which allows you to use the privileges from all roles that have been granted to your user, including the `immuta_` role and your current active primary role.
While data policies do replace original views with Immuta-managed view, the new view will be in the same database as the original view with the same name. So there is no impact to the way you must query an Immuta vs non-Immuta managed view.
---
# 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://documentation.immuta.com/SaaS/configuration/integrations/teradata/reference-guides/accessing-data.md?ask=&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.
