> 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-on-prem/8.13/multi-tenant/indicator-management-on-the-main-tenant.md).

# Indicator management on the main tenant

Manage main tenant indicators in Cortex XSOAR 8.13 On-prem.

From the main tenant, on the Threat Intel page, you can see the following tabs:

* Indicators
* Threat Intel Management (TIM) reports

The Threat Intel page shows all indicators and TIM reports across all child tenants.

{% hint style="info" %}

### Note

If you don't have a TIM license you can only view the Indicators tab.
{% endhint %}

You can't create indicators/TIM reports on the main tenant.

Although you can't investigate indicators directly, you can pivot to the indicator on the child tenant by clicking the indicator. You can also go to the child tenant's indicator page by clicking main tenant (top left of the window) and selecting the relevant child tenant.

By default, the **Indicators** page displays open indicators (from all child tenants) in the last seven days. You can filter this by changing the date and selecting the relevant tenant.

In the **Indicators** tab, you can do the following:

| Action      | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Export CSV  | Export the selected indicators to a CSV file. By default, the CSV file is generated in UTF8 format. Administrator permission is required to update server configurations, including changing the format, see [Export incidents and indicators to CSV using the UTF8-BOM format](/cortex-xsoar-8-on-prem/8.13/investigate-and-respond-to-threats/threat-intel-management/export-indicators.md#UUID-0ab7a802-f244-1ddf-9614-fcf9a3ff22d7_section-idm4551395919174434094455621277). |
| Export STIX | Export the selected indicators to a STIX file                                                                                                                                                                                                                                                                                                                                                                                                                                    |


---

# 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-on-prem/8.13/multi-tenant/indicator-management-on-the-main-tenant.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.