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

# Troubleshooting

Check the organization, active view, document type, search text and filter badges first. Refresh the list and check further result pages. If a control is still unavailable, ask your administrator to check your permissions and enabled modules.

**Ctrl/Cmd + K** opens the global quick search. **Ctrl/Cmd + Q** refreshes the dashboard and **Ctrl/Cmd + H** opens help. The gear menu contains the keyboard-shortcut reference. An organization-wide pending-document counter, when shown, is an administrator indicator; it is not your personal task count.

Use Ctrl on Windows/Linux and Cmd on macOS for the shortcuts below. Browser or operating-system shortcuts may take priority.

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/troubleshooting.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.