> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/marketplace/agreements/view-and-download-attachments.md).

# View or download agreement files

Access files related to your agreement.

The **Attachments** tab within the agreement details page shows all files associated with your agreement.

These files can include invoice PDFs, Excel files, license keys, or any other file added by SoftwareOne or the vendor. This topic describes how you can view and download these files.&#x20;

{% hint style="info" %}

* License keys can only be viewed and copied, not downloaded.
* If the agreement is still provisioning, the **Attachments** tab will be empty.
* You can only view and download agreement attachments. You cannot add new files.&#x20;
  {% endhint %}

### View or download the agreement files

To view or download agreement files:

1. Go to **Marketplace** > **Agreements**.
2. Select the required agreement.&#x20;
3. On the agreement details page, select the **Attachments** tab.&#x20;

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/Z5DNbniz33mXCZoO62Rm/blobs/Dwbo7TSKtltrfPAdV8oc/image.png" alt=""><figcaption><p>Use the Attachments tab to view and download files.</p></figcaption></figure></div>

4. Select the file name in the **Reference** column to download it to your system.&#x20;


---

# 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.platform.softwareone.com/modules-and-features/marketplace/agreements/view-and-download-attachments.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.
