> 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/onboarding-in-cortex-xsoar.md).

# Onboarding in Cortex XSOAR

Onboarding process for Cortex XSOAR 6.15.

After you have familiarized yourself with Cortex XSOAR concepts, you should start the onboarding process.

{% hint style="info" %}
For tips and how-to videos, go to the [LiveCommunity Customer Journey](https://live.paloaltonetworks.com/t5/customer-journey-xsoar/2-setup-xsoar/ta-p/394505). Also see the [Deployment Checklist - Best Practices](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/deployment-checklist-best-practices.md).
{% endhint %}

This section describes how to install and run Cortex XSOAR:

* [Installing the server](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/single-server-deployment.md): View the system requirements, install the server including Elasticsearch, install offline, upgrade, and uninstall.
* [Proxy](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/proxy.md): Follow the procedure in this section if you need a proxy for Cortex XSOAR.
* [Elasticsearch](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/elasticsearch.md): View the Elasticsearch requirements and how to set up Elasticsearch, including migration.
* [Docker](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/docker.md): Although Docker is installed with Cortex XSOAR for most operating systems, you may need to manually install Docker. You can also manage Docker images and view and apply Docker hardening.
* [Podman](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/podman.md): For some operating systems, Podman is installed with Cortex XSOAR, but you may need to manually install Podman.
* [High Availability](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/high-availability.md): Intended to keep your systems running even if one of the components in the system fails.
* [Disaster Recovery and Live Backup](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/disaster-recovery-and-live-backup.md): Enables you to mirror your production server to a backup server. In a disaster recovery situation, you can easily convert your backup server to be the production server.
* [Users and Roles](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/users-and-roles.md): Manage users and roles, set up a password policy, authenticate with SAML 2.0 and Active Directory.
* [Marketplace](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/marketplace.md): Manage content through content packs.
* [Remote Repositories in Cortex XSOAR](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/remote-repositories-in-cortex-xsoar.md): Configure a remote repository on a development and production machine and push content to a remote repository.


---

# 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/onboarding-in-cortex-xsoar.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.