> 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-6-threat-intel-management-guides/6.15/reports/threat-intel-reports/threat-intel-reports-management/publish-a-threat-intel-report.md).

# Publish a Threat Intel Report

Publish threat intelligence reports with read-only access in Cortex XSOAR 6.15.

When you have finished drafting a report, you can publish the report, which means all roles have read-only access to the report to prevent other users from making changes. If you unpublish a report, that access is reverted. Publish/unpublish does not revert any read/write access that you [granted to a specific role](/cortex-xsoar-6-threat-intel-management-guides/6.15/reports/threat-intel-reports/threat-intel-reports-management/rbac-for-reports.md).

1. Navigate to the Threat Intel Reports table and click the **Name** of the report you want to share.
2. From the Access section, **Publish** the report.

   Once published, anyone who you give the report link to can see the report (provided they have access to your Cortex XSOAR environment). To remove read-only access, **Unpublish** the report.


---

# 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-6-threat-intel-management-guides/6.15/reports/threat-intel-reports/threat-intel-reports-management/publish-a-threat-intel-report.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.