> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/request-management/manage-views.md).
# Manage views
Use the default Open and Closed views of the Requests tab, create custom tabs and filters, and share views with everyone, specific inboxes or keep them private
[The request tab](https://app.siit.io/requests?tab=fp_0u4qrtks) displays all your requests and the requests of your teams. You can switch between the following default views:
* **OPEN** - Includes requests that have been answered but are still active, such as those marked as New, In Progress, or Waiting.
* **CLOSED** - Contains all past requests that have been resolved.\
**OPEN** - Includes requests that have been answered but are still active, such as those marked as New, In Progress, or Waiting.
**CLOSED** - Contains all past requests that have been resolved.\
You also have the ability to create and save Custom Tabs and Filters to better organize your requests.
### Sharing
Views have different visibility settings:
* **Everyone** are shared with all admins.
* **My Inboxes** are shared with specific inboxes only.
* **Private** are only accessible to a single admin.
**Everyone** are shared with all admins.
**My Inboxes** are shared with specific inboxes only.
**Private** are only accessible to a single admin.
### Reordering
You can easily reorganize the tabs in the "All Views" pop-up. Simply drag and drop them to arrange the views as you prefer.
**Filter by read / unread**
You can filter any view by whether a request has been read. Add the **Read / Unread** filter to a view to focus on requests no one has opened yet, and switch it to **Read** to revisit ones you've already looked at. Pair it with a saved Custom Tab to keep a permanent “Unread” view for triage.
---
# 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.siit.io/guides/request-management/manage-views.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.
