> 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/evaluate/query-in-studio/save-as-perspective.md).

# Save as Perspective

Save a Studio query as a perspective to reuse, share, and serve through a Data API.

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. (To find perspectives others have saved, see [Discover → Perspectives](https://v2.dataos.info/consume/discover/search-the-hub/perspectives.md).)

## Save a query

You can save a perspective from any of the four Studio query modes: **Visual Builder**, **GraphQL**, **Semantic SQL**, or **Source SQL**. After running a query in [Studio](https://v2.dataos.info/consume/evaluate/query-in-studio.md), open the **Save as Perspective** dialog and give it an identity others can find and trust:

![Save as Perspective dialog showing name, description, tags, visibility, and auto refresh](https://540997223-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAxLuoblPBpNVcNU4lKPo%2Fuploads%2Fgit-blob-bb3d2f72419089e176212e60fddba3a0ab330090%2Fsave-as-perspective.png?alt=media)

* **Name** (required): how people recognize it.
* **Glossary term**: ties the perspective to a shared business definition.
* **Description**: what it returns, so consumers know whether it answers their question.
* **Tags**: make it easier to find and group.
* **Visibility**: who can use it. Keep it to **Only me** while drafting, or open it to share.
* **Auto refresh**: whether the result stays current automatically.

Select **Save**. When Studio confirms **Perspective created successfully!**, select **View details** to open the new perspective.

## Explore a perspective

The perspective page has four tabs and an **About** panel (description, product, visibility, owner, tags, and the models behind it):

| Tab      | What it gives you                                                                                                                    |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Data     | The result, with last-updated time and row and column counts, so you can confirm it returns what you expect                          |
| Columns  | Each field with its tags and profile, with a search box and a tag filter, so you understand it before building on it                 |
| Lineage  | A lineage graph of how the perspective is built; turn on **Columns** for column-level detail, so you can judge how trustworthy it is |
| Activate | The REST API endpoint, required `Authorization` header, and response schema to serve it into an application or report                |

The Activate tab is the bridge to activation: it gives you everything needed to consume the perspective programmatically. See [APIs](https://v2.dataos.info/consume/activate/apis.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/evaluate/query-in-studio/save-as-perspective.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.
