> 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

A Perspective is a saved, governed query built on a Data Product's semantic layer. It preserves the selected dimensions, measures, filters, and time window so the same result can be reused, shared, or consumed through a Data API.

This page covers how to **discover** existing Perspectives from the Hub. To learn how to create one from a query, see [Save as Perspective](/consume/understand/overview/perspectives.md).

## Switch the search scope to Perspectives

By default the Hub lists Data Products. To browse Perspectives, open the scope selector using the icon next to the search field and choose **Perspectives**.

<img src="/files/JFFb8yNltLYPVr3gIaWk" alt="Search scope selector with Perspectives selected" width="375">

The Hub then lists the Perspectives available in the selected Tenant as cards. Each card shows the Perspective icon, its name, and a short description, so you can tell at a glance whether one already answers your question.

<figure><img src="/files/CpjhNhA88Gk0fvi5X7fk" alt="Hub listing Perspectives as cards with the filter panel on the left"><figcaption><p>The Hub with the search scope set to Perspectives.</p></figcaption></figure>

## Filter Perspectives

When many Perspectives exist, the **Filter by** panel helps you reach the right one faster. Narrow the list by:

* **Refresh**: find Perspectives that stay current automatically versus those you refresh yourself.
* **Visibility**: focus on what is shared with **Everyone** or scoped to **Only Me**.
* **Data Product**: see only Perspectives built on the product you care about.
* **Tags**: group Perspectives by the conventions your team uses.
* **Owner**: find Perspectives maintained by a specific person you trust or can ask.

You can combine filters with keyword search to narrow the list further. See [Filters](/consume/discover/search-the-hub/filters.md) for how the filter panel works.

## Open a Perspective

Click a Perspective in the list to open its detail panel on the right and confirm it fits before you reuse it. The panel shows:

* **Description**: what the Perspective returns, so you can judge whether it answers your question.
* **Visibility**: whether the Perspective is **Public** or private, so you know who else relies on it.
* **Data Product**: the product the Perspective is built on, so you can trace it to a trusted source.
* **Owner**: the user who owns the Perspective, so you know who to ask about it.

<figure><img src="/files/k9ECaRpCnyzukFymYSlR" alt="Perspective detail panel showing description, visibility, data product, and owner"><figcaption><p>The Perspective detail panel.</p></figcaption></figure>

Select **Know more** to open the full Perspective page, where you can explore the **Data**, **Columns**, **Lineage**, and **Data APIs** tabs. See [Save as Perspective](/consume/understand/overview/perspectives.md) for details on the full Perspective page.

## Next steps

* [Metrics](/consume/discover/search-the-hub/metrics.md)
* [Save as Perspective](/consume/understand/overview/perspectives.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 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/consume/discover/search-the-hub/perspectives.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.