> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/administration/troubleshooting-and-support.md).

# Troubleshooting and Support

If you encounter any issues or need assistance, our support process is designed to provide you with the resources you need:

1. **Knowledge Base**: Explore our [Crobox Docs](/readme.md) for articles, FAQs, and step-by-step guides on common topics.
2. **Onboarding Resources**: Refer to your onboarding training materials, including recorded training sessions, for in-depth guidance on using the platform.
3. **In-App Hints**: Look for helpful information points within the app that provide quick tips and contextual guidance for various features.
4. **Contact Support**: If you need additional help, chat with the Crobox team using the chat icon in the top bar of the Crobox App.

We’re here to ensure you have the support and resources required for your success.


---

# 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.crobox.com/administration/troubleshooting-and-support.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.