> 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.14/learn-about-cortex-xsoar/get-started-in-cortex-xsoar/new-user-faq.md).

# New User FAQ

The following are frequently asked questions for new Cortex XSOAR users.

<details>

<summary>How do I import custom content (received from a colleague or the Customer Success team, exported from a different Cortex XSOAR system, etc.) into Cortex XSOAR?</summary>

If you have a full content bundle (.tar.gz file), navigate to Settings → About → **Troubleshooting** and scroll to the bottom of the page. Under **Custom content**, click or drag and drop into the **Import** box.

You can also import specific content types, such as playbooks, by navigating to that section of Cortex XSOAR and then clicking the upload button in the upper right corner of the page.

</details>

<details>

<summary>How do I export custom content from Cortex XSOAR so I can share it?</summary>

Navigate to Settings → About → **Troubleshooting** and scroll to the bottom of the page. Under **Custom content**, click **Export** to download a compressed file containing all of the custom content from your instance.

You can also export individual content items, such as playbooks, by selecting the content item, clicking the triple dot menu in the upper right corner of the page, and clicking the **Download** button.

</details>

<details>

<summary>What is a Cortex XSOAR log bundle and how do I download one?</summary>

A [log bundle](/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/logs/create-a-log-bundle.md) is a set of logs that capture data points about your Cortex XSOAR environment. These logs provide information that is useful for troubleshooting and working with support. To download a log bundle, navigate to Settings → About → **Troubleshooting**. At the top of the page, click **Download logs**

</details>

<details>

<summary>The command I’m trying to run isn’t working. How do I troubleshoot?</summary>

Most Cortex XSOAR commands and automations support the hidden argument **`debug-mode=true`**, which you can add onto the command line to have Cortex XSOAR generate a debug log for the script execution. See the [Troubleshooting Guide](https://xsoar.pan.dev/docs/reference/articles/troubleshooting-guide) for more details.

</details>

<details>

<summary>How do I configure my Cortex XSOAR notifications settings?</summary>

Navigate to your profile picture icon at the bottom of the side menu and click on **Notifications**. By default, all notifications are enabled. Deselect the checkboxes for notifications you don’t want to receive.

</details>

<details>

<summary>How do I get notifications via Slack/Teams/other chat application?</summary>

Configure an integration instance for that chat application. As long as the integration instance implements the **`send-notification`** command, it will appear on the **Notifications** page.

</details>

<details>

<summary>What is the difference between a dashboard and a report?</summary>

Dashboards show data from a rolling, relative time-frame from a certain time in the past (for example, 7 days ago) through the present and are shown when you log into Cortex XSOAR. Reports allow you to share similar data outside of Cortex XSOAR via email. Reports can be scheduled to run at a specific time to capture data where the start/end time is important. For example, if management requests a report on the incidents that occurred between 08:00 yesterday and 08:00 today.

</details>

<details>

<summary>How do I access the playground?</summary>

The link to the playground appears under the **Incidents I own** icon in the left sidebar. You can also access the playground at the URL **`https://<SERVER>/#/WarRoom/playground`** or by accessing the shortcut menu using **`CMD–K`** and selecting **Playground**.

</details>

<details>

<summary>How do I update all of my installed Cortex XSOAR content packs at the same time?</summary>

Navigate to Marketplace → **Installed Content Packs**. From the **Show** dropdown, select **Update available**. Click the checkbox to select all, then click the **Update** button.

</details>

<details>

<summary>How do I search for incidents/indicators/playbooks/automations/etc. in Cortex XSOAR?</summary>

Cortex XSOAR comes with a powerful [search](/xsoar-6-administrator-guide/6.14/learn-about-cortex-xsoar/get-started-in-cortex-xsoar/how-to-search.md) capability that uses the Lucene query syntax. For example, to search playbooks:

* Search for the playbook with the exact name “Phishing - Generic v3”: **`name:"Phishing - Generic v3"`**
* Search for playbooks where the word “Phishing” appears anywhere in supported system objects: **`Phishing`**
* Search for playbooks where the playbook name contains “Phishing”: **`name:"Phishing"`**

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/learn-about-cortex-xsoar/get-started-in-cortex-xsoar/new-user-faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
