# Add attachments to a document

Learn how to add supporting files and links to your GetAccept document.

June 1, 2026

## Adding a Sender Attachment to your document

Sender attachments are files that **recipients can or must view** during the signing process, ideal for sharing important documents like terms, instructions, or policies.

### How to add a Sender Attachment

1. While preparing your document, click the **Add** tab in the top-right corner.
2. Select **Add attachment**.

3. Choose to:
   - Upload a new file
   - Use a file from your **attachment library**
   - Add an external link

4. Optionally, check **Save attachment to Attachment library** to save it for future use.

5. Give the attachment a **title**.
6. Choose:
   - **Which recipients** should see the file (everyone or selected recipients)
   - Whether **viewing is required** before signing
7. Click **Save**.

🔒 If viewing is required, the selected recipients will need to open the attachment before they’re able to sign.

## Adding a Recipient Attachment to your document

Recipient attachments are files that recipients **can or must upload** as part of the signing process, great for collecting NDAs, ID cards, tax forms, or licenses.

Note: Recipient attachment is an Enterprise feature

### How to add a Recipient Attachment

1. Click the **Add** tab
2. Select **Add recipient attachment**

3. Choose:
   - **Who** needs to upload the file (selected recipients or “Everyone”)
   - Whether the upload is **required before signing**
   - Whether the uploaded file should be **private** (only visible to the sender and that recipient)

Use privacy when you want each recipient's upload to remain confidential.

## Supported recipient attachment use cases

- **Specific recipient _must_ upload** (Mandatory before signing for a selected recipient)
- **Specific recipient _must_ upload + private** (Mandatory upload, visible only to sender and selected recipient)
- **Specific recipient _can_ upload** (Optional upload from a specific recipient)
- **Specific recipient _can_ upload + private** (Optional and private between sender and recipient)
- **Several recipients _must_ upload** (Mandatory from multiple selected recipients; each file saved individually)
- **Several recipients _must_ upload + private** (Mandatory; each file is saved privately between sender and uploader)
- **Several recipients _can_ upload** (Optional upload for selected recipients)
- **Several recipients _can_ upload + private** (Optional and private between sender and each uploader)
- **Everyone _can_ upload** (Any recipient can upload; only the most recent file is saved)
- **Everyone _can_ upload + required** (At least one upload is required before the last signer; only the most recent file is saved)

## Attachment visibility and privacy

- **Private** attachments are only visible to the **sender and the uploading recipient**
- **Shared** attachments are visible to **all recipients**

You can **mix and match** required/optional, shared/private settings to match your use case.

## Using the Attachment Library

The attachment library shows:
- If an attachment is **shared or private**
- **When** the file was created
- **Who uploaded** the file

You can reuse previously added attachments and manage your document assets more efficiently.

## File Fingerprint & Certificate

Once a contract is signed:
- All attachments (sender and recipient) will be shown in the certificate under **Supplemental files**
- They are accessible via permanent links
- Each file includes a **file fingerprint** that matches the certificate (as shown in the screenshots below)

|     |     |
| --- | --- |
|  |  |

## Reordering attachments

You can change the order of attachments by **clicking and dragging**, or by selecting the three dots icon on an attachment.

## FAQ

**How long are attachments available?**

Attachments are available indefinitely.

**How long does the link in the certificate last?**

The attachment link in the certificate is permanent and does not expire.

**What happens to attachments if the contract is deleted?**

Even if the contract is deleted, customers can still access attachments via the certificate.

**Can I make a sender attachment both private and required?**

You can select who sees the attachment and make viewing required, but currently, sender attachments are not private in the same way as recipient uploads.

**Can I require _all_ recipients to upload individually?**

Not currently. You can assign attachments to several selected recipients, but not enforce that every recipient must upload.

**What happens when I assign an attachment task to “Everyone”?**

All recipients will have the option to upload an attachment during the signing flow. However, only the last uploaded file will be saved.

**When I assign an attachment task to “Everyone”, can multiple recipients upload attachments at the same time?**

Yes, but each new upload will overwrite the previous one. Only the final (most recent) file will be retained and attached to the document and audit trail.

**What if no one uploads the file?**

If the attachment is required, the contract cannot be signed unless at least one recipient uploads a file. The last signer will be forced to upload if no one else has done so.

**Why would I choose “Everyone” instead of assigning to a specific recipient?**

Use “Everyone” when you know an attachment is needed (e.g., an NDA) but you’re not sure which recipient will provide it. This gives all recipients the opportunity to upload without assigning responsibility to a specific person.

**Is the “Everyone” setting compatible with private attachments?**

No. The "Everyone" setting does not support privacy per recipient. The uploaded file will be visible to all recipients unless you assign the attachment to specific recipients and mark it as private.

**Can I see who uploaded the final saved file?**

Yes. The audit log will indicate who uploaded the final file that was attached to the document.