> 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/overview-of-uploaded-documents.md). # Overview of Uploaded Documents The dashboard is your daily worklist in DocBits. Find imported documents, check their status, open them for validation and organize the work with your team.

The current dashboard: search and tools at the top, saved views and document types below, and the document table. Document values are hidden for privacy.

Each row represents a document. Depending on your column configuration, it shows its name, status, document type, invoice data, supplier, assignee, dates and amounts. Click a sortable column header to change the order. Scroll horizontally to see more columns and use the page controls and **Documents per Page** at the bottom to move through the results. If grouping is available, select a grouping field above the table. For date fields, choose day, week or month. Open a group to see its documents, or remove the grouping to return to the flat list. Use the **+** next to the document-type tabs to show additional tabs. The tabs can be reordered by dragging. Removing a tab changes your view; it does not delete documents. Open the gear icon and the column-settings button to choose visible columns, move columns between the hidden and visible lists, and drag visible columns into order. You can also add fields from a document type. See [Change document columns](/end-user-and-partner-section/end-user-section/dashboard/change-document-columns.md). For searching, document actions and saved views, return to the [dashboard guide](/end-user-and-partner-section/end-user-section/dashboard.md). --- # 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/overview-of-uploaded-documents.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.