> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/features/views.md).

# Views

Quickly access and organize your resources in the Catalog and Search with customizable personal and team Views

## Managing Views

You can save filters for quick access to common searches and subsets of resources in the catalog. These can be personal or shared with your team.

### **Catalog Views**

1. Click into the Catalog and select relevant filters to add.
2. Click **Save view** in the top right.
3. Title the filtered view and set the Team visibility (Optional). If you leave the "Team visibility" section blank, these will only be saved to your personal space.
4. Access previously created Views in the top left of Catalog under **All results**.

**Note:** Personal views are only visible to you and can be used to customize your workspace without affecting team settings.

<figure><img src="https://secoda-public-media-assets.s3.amazonaws.com/bb1ac275-69ca-49ae-a752-6d8121e14cae.gif" alt=""><figcaption></figcaption></figure>

### **Search Views**

1. Click into Search and select relevant filters to add.
2. Click 'Save view' in the top right.
3. Title the filtered view and set the Team visibility (Optional). If you leave the "Team visibility" section blank, these will only be saved to your personal space.
4. Access previously created Views in the top left of search under **All results**.

**Note:** Personal views are only visible to you and can be used to customize your workspace without affecting team settings.

<figure><img src="https://secoda-public-media-assets.s3.amazonaws.com/ed5703e1-28ce-4cdd-bc2f-2b03586cd135.gif" alt=""><figcaption><p>Search Views</p></figcaption></figure>


---

# 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://docs.secoda.co/features/views.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.