> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/end-user-and-partner-section/end-user-section/dashboard/personal-dashboards.md). # Personal Dashboards Save a recurring worklist with its filters, sort order and visible columns. A saved dashboard is a view of existing documents. ## Create and share a view 1. Set the search, filters, document type, sorting and columns you want. 2. Open the blue view badge below the search box. 3. Choose **Create New Dashboard** and enter a clear name. 4. Select private visibility, all users, or specific groups and users. 5. Choose **Save**. The visibility setting controls who can use the view. Each person still sees only the documents their permissions allow.
Create a named dashboard and choose who can see it.

Create a named dashboard and choose who can see it.

## Switch, update or remove a view Use the view badge to select a saved dashboard or return to the default view. After changing your own view, choose **Save Dashboard Changes** when that action becomes available. It is unavailable when nothing has changed or when another person shared the view with you. Use the edit control for a view you own to change its name or sharing settings. Use its delete control and confirm only when you want to remove the saved view. Removing a view does not delete the documents. To adapt somebody else's shared view, create a new view of your own. --- # 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.docbits.com/end-user-and-partner-section/end-user-section/dashboard/personal-dashboards.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.