> 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.12/learn-about-cortex-xsoar/get-started-in-cortex-xsoar/licenses.md). # Licenses Cortex XSOAR requires a yearly license per user, with the exception of the Cortex XSOAR Community Edition. Multi-year licenses are available. You can view and download your license from the [Cortex Gateway](https://cortex-gateway.paloaltonetworks.com/accounts). {% hint style="info" %} ### Note Only users with the Super User role in CSP or the Account Admin role in Cortex can download the license. After your license expires, you have a 7-day grace period which gives you time to add your new license before the current license expires {% endhint %} #### License Usage This table describes the types of Cortex XSOAR licenses that are used in the following circumstances: | Version | Usage | | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Cortex XSOAR Community Edition |

For evaluating Cortex XSOAR, partner development, and general free usage.

Note

Cortex XSOAR Community Edition is EoL on August 15, 2024.

| | Cortex XSOAR Threat Intel Management Edition | Built for Threat Intelligence & Security Operations teams who need threat intelligence-based automation. | | Cortex XSOAR Starter Edition | Built for Security Operations and Incident Response customers who need case management with collaboration and playbook-driven automation | | Cortex XSOAR Edition | Built for customers who need a complete security automation solution. | #### License Quota The following table describes the license quotas of each version in Cortex XSOAR. The license includes the number of users that can be configured. Self service read-only users do not count as users in your license pool. ![comparison-matrix.png](/files/VJP0ZEdxpYnS8MFbsBDJ) {% hint style="info" %} ### Note Intel feed quotas are based on the selected **Fetches Indicators** field in the integration instance settings, not the enabled status. Disabling an integration instance does not affect the Intel feed quota. For example, if the AWS Feed is enabled and is fetching indicators and you don't want to include this in your quota, open the integration settings and deselect the \*\*Fetches Indicators \*\*checkbox. {% endhint %} #### Multi-Tenant Licenses XSOAR TIM, XSOAR Starter Edition, and XSOAR are all available for multi-tenant deployments, with a multi-tenant license. Cortex XSOAR multi-tenant deployments are designed for MSSPs (managed security service providers) and enterprises that require strict data segregation, but also need the flexibility to share and manage critical security practices across tenant accounts. #### Users For license purposes, Cortex XSOAR includes the following users: * Audit users Audit users have read-only permission in Cortex XSOAR, so they do not have the ability to edit system components and data, or run commands, automations, and playbooks. Audit users can view incidents, dashboards, and reports. This should be used for example, by SOC managers who do not need to investigate incidents, change data, etc. * Full users Full users have read-write permission in Cortex XSOAR, meaning they have the ability to view and edit system components and data. They can investigate incidents, run automation scripts and playbooks, chat in the War Room, etc. For more information about roles, see [Users and Roles Overview](/xsoar-6-administrator-guide/6.12/onboard-cortex-xsoar/onboarding-in-cortex-xsoar/users-and-roles/users-and-roles-overview.md). {% hint style="info" %} ### Note Self-service read-only users are not counted in your license. {% endhint %} --- # 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.12/learn-about-cortex-xsoar/get-started-in-cortex-xsoar/licenses.md?ask=&goal= ``` `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.