> 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/cortex-xsoar-8-saas/onboard-cortex-xsoar/plan-and-prepare-your-deployment.md).

# Plan and prepare your deployment

Before deploying your tenant, consider your use case and what you need to optimize your tenant for Cortex XSOAR 8 SaaS.

Before you start your Cortex XSOAR 8 SaaS deployment, consider the following:

<details>

<summary>Do you need Cortex XSOAR to communicate with internal or external applications that a firewall or proxy may block?</summary>

You may need to create an engine to enable communication or load balancing.

</details>

<details>

<summary>Do you need a repository for content development?</summary>

Subject to your license, you can activate a development tenant and use either the built-in remote repository or a private remote repository (Git-based) to test and develop content before using it in a production environment.

</details>

<details>

<summary>How do you want users to access Cortex XSOAR? Do you need to set up SSO?</summary>

</details>

<details>

<summary>Do you need to restrict user roles to certain actions?</summary>

</details>

<details>

<summary>How do you want to secure requests between main and child tenants (for multi-tenant) or your content management?</summary>

Do you want to use SSL or a self-signed certificate?

</details>

<details>

<summary>How do you want to communicate with users in Cortex XSOAR?</summary>

Cortex XSOAR comes out-of-the-box with the Mail Sender integration. It enables the tenant to send notification emails for system updates, incidents, playbooks, and tasks. Do you want to set up an alternative mail sender? Do you want to integrate a communication app, such as Slack?

</details>

<details>

<summary>What steps do you currently take in your day-to-day SOC operations? Which integrations will enable you to automate your most important and time-consuming procedures?</summary>

</details>


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-saas/onboard-cortex-xsoar/plan-and-prepare-your-deployment.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.