> 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/understand/overview/perspectives.md).

# Save as Perspective

After running a query in [Studio](/consume/understand/overview.md), save it as a Perspective so the same selection can be reused, shared, or consumed through a Data API. To discover Perspectives others have already saved, see [Perspectives in the Hub](/consume/discover/search-the-hub/perspectives.md).

## Save a query as a Perspective

After running a query in the [Studio](/consume/understand/overview.md), save the current selection as a Perspective so you never have to rebuild it. The **Save as Perspective** dialog lets you give it an identity others can find and trust:

![Save as Perspective dialog showing name, description, tags, visibility, and auto refresh](/files/9eMAEAho7pUdUGISgBYe)

* **Name**: how people will recognize the Perspective (required).
* **Glossary term**: an optional glossary term so the Perspective ties to a shared business definition.
* **Description**: what the Perspective returns, so consumers know whether it answers their question before opening it.
* **Tags**: labels that make the Perspective easier to find and group.
* **Visibility**: who can use it — for example, keep it to **Only me** while drafting, or open it up to share.
* **Auto Refresh**: whether the result stays current automatically, so consumers always see up-to-date numbers.

Select **Save**. A confirmation appears, and you can select **View details** to open the new Perspective.

![Confirmation that the Perspective was created successfully](/files/QJLiPgmQSs8t12LnF5dP)

## Explore a Perspective

The Perspective page opens with **Data**, **Columns**, **Lineage**, and **Data APIs** tabs, and an **About** panel showing the description, product, visibility, owner, tags, and the models the Perspective is built on.

### Data

The **Data** tab lets you confirm the Perspective returns what you expect and how current it is, showing the result alongside the last-updated time, row count, and column count.

![Perspective Data tab showing the result table and About panel](/files/Ve9903oqfGbwP2RODA2c)

### Columns

The **Columns** tab lets you understand each field before you build on it, listing the columns with their tags and profile.

![Perspective Columns tab listing the columns and the models that back them](/files/otraIxK3oEhR7vu61k7Z)

### Lineage

The **Lineage** tab lets you trace where the result comes from, so you can judge how trustworthy it is, by showing how the Perspective is built from the underlying inputs, outputs, and semantic models.

![Perspective Lineage tab showing the upstream models](/files/tXnumL5FnP3FP80jFzfw)

### Data APIs

The **Data APIs** tab gives you everything needed to serve the Perspective into an application or report — the endpoint to fetch the result, the required `Authorization` header, and the response schema.

![Perspective Data APIs tab showing the access endpoint, headers, and response schema](/files/FOjA73HcVjpDu3I2qqQ6)


---

# 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/understand/overview/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.