> 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/consume/discover/search-the-hub/perspectives.md).

# Perspectives

Find and open the saved, governed queries built on a Data Product.

A perspective is a saved, governed query on a Data Product. It preserves the query you ran, so the same result can be reused, shared, or consumed through a Data API. Perspectives can be saved from any of the four Studio query modes: Visual Builder, GraphQL, Semantic SQL, or Source SQL.

This page covers how to **find** existing perspectives. To create one from a query, see [Save as Perspective](https://v2.dataos.info/consume/evaluate/query-in-studio/save-as-perspective.md).

## Find perspectives on a product

Perspectives live on the Data Product they are built on. Open a product from the Hub (select its card, then **More details**), then use either of these:

* **Jump to > Perspectives** in the product header lists the product's perspectives as cards, each with its name and description. Use the toggle at the right to switch between cards and a list.
* The **Perspectives** card in the product's **Adoption** section lists perspectives by name and description. Select **View all** to see every perspective on the product.

![Perspectives view on a Data Product](https://540997223-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAxLuoblPBpNVcNU4lKPo%2Fuploads%2Fgit-blob-420f6186212879a923a3d0b2d8458d9858c67076%2Fdp-perspectives-view.png?alt=media)

## Open one

Select a perspective to open its page.

![Perspective page with Data, Columns, Lineage, and Activate tabs and the About panel](https://540997223-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAxLuoblPBpNVcNU4lKPo%2Fuploads%2Fgit-blob-0736ff4268cc52d82c86c2565cb04aac7ff72ae5%2Fperspective-page.png?alt=media)

The page has four tabs:

* **Data:** the result, with the last-updated time and row and column counts. Search, download, or expand the table from the icons above it.
* **Columns:** each field with its tags and profile. Search the columns or filter by tag.
* **Lineage:** a lineage graph of how the perspective is built. Turn on **Columns** for column-level detail.
* **Activate:** the REST API endpoint and `Authorization` header to copy into your application, a link to create an API token, and the response schema.

The **About** panel on the right shows the description, the Data Product it is built on, visibility (for example, **Public** or **Private**), owner, and tags. **Models** lists the models behind it. See [Save as Perspective](https://v2.dataos.info/consume/evaluate/query-in-studio/save-as-perspective.md) for more.

Next: [Metrics](https://v2.dataos.info/consume/discover/search-the-hub/metrics.md).


---

# 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/consume/discover/search-the-hub/perspectives.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.
