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

# Product Overview

Birds Document Warehouse, also known as Raptor Document Warehouse or 9A Raptor DWH in the legacy documentation, manages documents and other unstructured information in the context of your business processes.

The solution integrates with Microsoft Dynamics 365 applications so that users can archive, find, and consult documents without losing the business context that makes those documents relevant. Documents can be added through the web application, integrated applications, and automated processes.

## Business context and document access

Document Warehouse organizes documents using metadata, tags, and taxonomy. These provide a common way to classify information from internal and external sources and make it available to the users who need it. Roles and permissions determine which documents and configuration options a user can access.

## Connected applications

The legacy documentation covers integrations with Dynamics 365 Finance and Operations, Customer Engagement, and Business Central, as well as SharePoint, document processing, and custom API integrations.

## Cloud service

Birds Document Warehouse is delivered as Software as a Service on Microsoft Azure.

## Documentation terminology

Existing screenshots, application labels, endpoints, and release notes may still use the Raptor or 9A branding. Those names refer to the product documented here; names of settings and technical interfaces are retained where they are needed to follow the instructions.

For instructions on finding, viewing, and adding documents, see the [User Guide](https://docs.dynalogic.com/birds-document-warehouse-product-overview/user-guide.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.dynalogic.com/birds-document-warehouse-product-overview/readme.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.
