> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/engines/configure-engines/configure-access-to-communication-tasks-through-an-engine.md).

# Configure Access to Communication Tasks through an Engine

Configure communication task access through a Cortex XSOAR 6.15 engine.

You can use engines to enable users who do not have access to the Cortex XSOAR server to access the forms sent out in communication tasks. In such instances, the engine serves as a proxy and passes the information in the forms to the Cortex XSOAR server. To use your own certificate instead of the default self-signed certificate, [configure an engine to use custom certificates](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/engines/configure-engines/configure-an-engine-to-use-custom-certificates.md).

**Prerequisites**

Ensure that the **`BindAddress`** in the engine d1.conf file [is configured to a port](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/engines/configure-engines/common-properties-when-editing-an-engine-configuration.md) on which the engine can listen. The engine server address and the configured **`BindAddress`** are required to enable external users to communicate with the Cortex XSOAR server.

1. Navigate to Settings → About → **Troubleshooting**.
2. Click **Add Server Configuration**.

   | Key                                 | Value                                                                                        |
   | ----------------------------------- | -------------------------------------------------------------------------------------------- |
   | **`data.collection.external.link`** | The address (including the https prefix) of the engine used for external user communication. |
   | **`condition.ask.external.link`**   | The address (including the https prefix) of the engine used for external user communication. |
3. Click **Save**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/engines/configure-engines/configure-access-to-communication-tasks-through-an-engine.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 `build a script that syncs our docs to a CMS` 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.