> For the complete documentation index, see [llms.txt](https://docs.soda.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soda.io/manage-issues/browse-datasets.md).
# Browse datasets
The **Datasets** page displays **all datasets that have been onboarded into Soda Clou**d—either through publishing a contract or via the [onboarding process](/onboard-data-sources-and-datasets/onboard-datasets-on-soda-cloud.md).
It provides a quick overview of each dataset’s health, showing at a glance if a dataset has **issues**, **how many checks** from its contract **are failing**, how many **anomalies** were detected through metric monitoring, and **when the last scan was executed**.
You can filter datasets by properties like data source, owners, arrival time, attributes, or flags such as failures or anomalies. Use the search bar to quickly find a specific dataset by name, and sort the list by name, creation time, or data quality status.
> Learn more about [custom attributes](/dataset-attributes-and-responsibilities.md).
You can also sort the datasets list by name, creation date, check failures, or arrival time, among other options, to prioritize your focus.
## Customize your datasets' view
You can **tailor the Datasets view** to focus on the areas that matter most to you:
{% stepper %}
{% step %}
Use the **filter options** to narrow down the view.
{% endstep %}
{% step %}
Click the **Save** button to store your current filter configuration as a **collection**. Enter a **name** for the collection and click **Save**.
{% endstep %}
{% step %}
Once saved, your collection will be available in the **dropdown at the top right** of the dashboard. Simply select it to switch views.
{% endstep %}
{% step %}
Use the **context menu** next to the collection name to:
* **Delete** the collection if it’s no longer needed.
* **Share** the collection with others in your organization.
{% endstep %}
{% endstepper %}
***
{% if visitor.claims.plan === 'datasetStandard' %}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Dataset Standard license** documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
{% endhint %}
{% endif %}
{% if visitor.claims.plan === 'enterprise' %}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Team license** documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
{% endhint %}
{% endif %}
{% if visitor.claims.plan === 'enterpriseUserBased' %}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Enterprise license** documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
{% endhint %}
{% endif %}
{% if !(visitor.claims.plan === 'enterprise' || visitor.claims.plan === 'enterpriseUserBased' || visitor.claims.plan === 'datasetStandard') %}
{% hint style="info" %}
You are **not logged in to Soda** and are viewing the default public documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
If you do have a Soda license, make sure to **log in to Soda Cloud in this same browser**.
{% endhint %}
{% endif %}
---
# 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://docs.soda.io/manage-issues/browse-datasets.md?ask=&goal=
```
`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.