> 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/dashboard-tools.md).

# Dashboard Tools

The toolbar is beside the dashboard search. Hover over an icon to see its label. On narrower desktop windows, open **More** for additional actions.

| Tool                     | Use                                                                                                                                                 |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Refresh                  | Reload the list and statuses. A change indicator on the refresh button means newer data is available.                                               |
| Advanced settings (gear) | Open column settings, the keyboard-shortcut reference and the email import log. Organization-wide settings require administrator access.            |
| Scan document            | Open the scanner dialog when document scanning is enabled and a compatible scanner is available. Choose a device and scan settings before starting. |
| Analytics                | Show the dashboard status statistics. Select a status category to narrow the list.                                                                  |
| Start email import       | Start an import using the organization's existing mailbox configuration. This does not configure a mailbox.                                         |
| Export this table        | Request a CSV or Excel export when enabled. Save changes to a personal dashboard's columns first; the export reads its saved column configuration.  |
| Upload                   | Open the file dialog, select or drop files, optionally choose Classify As, then start the upload.                                                   |

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-637924c7efd08312872eb230bbf45a1a16e19bee%2Fdashboard-upload.png?alt=media" alt="Upload files and optionally choose their document type before importing."><figcaption><p>Upload files and optionally choose their document type before importing.</p></figcaption></figure>

The import log helps you check email imports. Filter it by subject or sender and inspect the available import information. A successful table-export request confirms that the request was submitted; it does not mean that a document was exported to your ERP.

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/dashboard-tools.md?ask=<question>&goal=<user_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.
