> 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/d365-customer-engagement/environment-setup.md).

# Environment Setup

The Environment Setup links and authenticates your Dynamics CE environment with a Raptor tenant.\
To do this, fill in the required parameters:\
\
**Development**: this checkbox should only be toggled on for development environments. Checking the 'Development' option will allow you to publish Raptor tabs on to your own forms, allowing users to open Raptor on the form using a tab.

{% hint style="warning" %}
Publishing a Raptor tab on your form creates an unmanaged layer. This is why the 'Development' setting should only be turned on for development environments.
{% endhint %}

**API URL**: the URL of the Raptor API environment which you're connecting to. Customers can always set this to <https://raptor.9altitudes.com/apigateway>

**External system**: the ID of your external system. See [External Systems](https://docs.dynalogic.com/birds-document-warehouse-product-overview/setup-and-configuration/external-systems.md)

**Secret**: the secret of your external system. See [External Systems](https://docs.dynalogic.com/birds-document-warehouse-product-overview/setup-and-configuration/external-systems.md)

**Act behalf of**: the user which will be used for background operations in Raptor. Make sure this user was added to your Raptor tenant with the external system assigned.

After clicking 'Validate', you should see a message 'You are connected to the 9A Raptor Document Warehouse'.

{% hint style="info" %}
In case an error occurs, check if:

* The ID and secret of your external system are correct
* The 'Act behalf of' user was added in Raptor with the external system assigned
  {% endhint %}


---

# 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/d365-customer-engagement/environment-setup.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.
