> For the complete documentation index, see [llms.txt](https://docs.debricked.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.debricked.com/product/exporting-sbom/sca-summary-export-pdf.md).
# SCA summary export (PDF)
Learn how to generate executive PDF reports from Global View.
### Overview
SCA Summary reports provide leadership-ready security summaries in PDF format.
Use them to share key security insights with stakeholders in a format that is easy to review and distribute.
{% hint style="info" %}
PDF export is currently available only for **Global export**.
{% endhint %}
### Generate an SCA summary report
To generate an SCA summary report:
1. Click **Generate Export** on the top right corner of the page.
2. Under **Scope**, select **Global export**.
3. Under **Export type**, select **SCA Summary**.
4. Click **Generate**.
5. Wait for the confirmation message.
6. Check the email connected to your OpenText Fortify SCA account.
The export starts generating immediately.
The PDF report is sent by email and may take a few minutes to arrive.
### What the report provides
The SCA summary report gives you a high-level summary of your organization’s security posture.
Use it when you need to:
* Share security status with leadership.
* Provide a concise summary for stakeholders.
* Distribute a snapshot of Global export data.
---
# 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://docs.debricked.com/product/exporting-sbom/sca-summary-export-pdf.md?ask=&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.
