> For the complete documentation index, see [llms.txt](https://docs.selectstar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.selectstar.com/getting-started/clean-up.md).
# 3. Hide Unwanted Datasets
In Select Star, you can hide datasets created in personal spaces, that are used for testing purposes or that aren't relevant to the entire company. Learn how to here.
Hide datasets created in personal spaces, or for testing purposes which aren't relevant to the entire company.
Click the name of your database in the **left sidebar** to see all the schemas and tables in your data warehouse.
Use `Cmd/Ctrl+F` to open a filter where you can search for specific datasets to remove, or use the filters in the right sidebar to show items with the lowest popularity.
This can help identify un-used datasets or datasets only used for testing purposes.
Select the datasets you'd like to hide (Use `Shift` on your keyboard to select consecutive items) and click the **Hide** button.
You'll be prompted to confirm before deleting.
You'll be able to add the data back if you need to later. See this page on [managing data sources](/data-source-management/manage-data-sources.md) for more information.
---
# 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.selectstar.com/getting-started/clean-up.md?ask=&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.
