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

# Training and Support

Use the documentation according to your role and the task you need to complete. Start with the web application's everyday tasks before changing shared tenant or integration settings.

## For Document Warehouse users

Review the [User Guide](https://docs.dynalogic.com/birds-document-warehouse-product-overview/user-guide.md). Practice finding a document, reviewing its business context, and using the permitted upload and sharing actions.

## For administrators and implementers

Review [Setup and Configuration](https://docs.dynalogic.com/birds-document-warehouse-product-overview/setup-and-configuration.md) for roles, users, classification, external systems, jobs, and storage. Use the connector-specific articles for the business application you administer.

## When asking for help

First review [Troubleshooting and Known Issues](https://docs.dynalogic.com/birds-document-warehouse-product-overview/troubleshooting-and-known-issues.md). Describe the expected result, what happened instead, the affected tenant and application, and the steps needed to reproduce the issue.

Share error messages and relevant timestamps, but remove passwords, tokens, external-system secrets, and confidential document content. Access and configuration changes should be handled by an administrator with the appropriate permissions.


---

# 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.dynalogic.com/birds-document-warehouse-product-overview/training-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.
