Attachment Types & Logic

Understanding sender attachments, recipient attachments, and private vs shared behavior

June 1, 2026

Attachments in GetAccept let you include additional documents, collect files from recipients, and control who can view or upload information. This article explains the types of attachments, who they belong to, and how visibility rules work.

1. Attachment Types

There are two main attachment categories in GetAccept:

1. Sender Attachments

Files added by the sender for recipients to view.

Use sender attachments when:

• You want to include additional documentation (terms, guides, brochures).
• You want one or more recipients to read supporting materials before signing.

Sender attachments never require recipients to upload anything, they only read or download.

2. Recipient Attachments

Files that recipients must upload as part of the signing or review process.

Use recipient attachments when:

• You need recipients to provide documentation (ID, certificates, forms, proofs).
• You want to collect specific files before they can complete signing.

Recipient attachments return uploaded files back to the sender in the completed document record.

2. Assignment Logic

Each attachment type can be connected to specific people in the flow.

Sender Attachments → Assigned to Viewers, Approvers, or Signers

• You choose which recipients can see the file.
• You can mark the attachment as required to view before signing.
• Recipients cannot edit, replace, or upload anything in response.

Recipient Attachments → Assigned to One or Multiple Recipients

• Only assigned recipients see this upload request.
• If marked required, the signer cannot finish until they upload a file.
• Multiple recipients can have separate or shared upload requirements depending on your setup.

3. Private vs Shared Attachments

Attachment visibility determines who can see uploaded files.

Private Recipient Attachments

Only the sender and the specific uploading recipient can see the file.

Use private mode when:

• Documents contain personal information (ID, banking data).
• You need compliance-safe one-to-one file collection.
• Multiple signers must upload different files that shouldn’t be visible to each other.

Shared Recipient Attachments

All assigned recipients and the sender can see the uploaded file.

Use shared mode when:

• Multiple people must review the same uploaded document.
• You want transparent collaboration between recipients.
• The uploaded file has no sensitive or personal information.

4. Required Rules

Both attachment types support required logic but behave differently:

Required Sender Attachments (view requirement)

• Recipients must open the attachment to proceed.
• Signing is blocked until the file is viewed.

Required Recipient Attachments (upload requirement)

• The assigned recipient must upload a file.
• Signing is blocked until the upload is completed.

Required rules ensure the right person performs the expected action at the correct moment.

5. Behavior in the Signing Flow

If a sender attachment is shared with a recipient:

• It appears in the signing experience as a supporting file.
• If required, the signer must open it.

If a recipient attachment is assigned:

• The signer sees an upload request during signing.
• If required, signing cannot finish without completing the upload.
• If private, other signers have no visibility or awareness of the uploaded file.

If multiple recipients each have separate attachment requests:

• Each signer sees only their own assigned requirements.
• The sender sees all uploads once completed.

6. Best Practices

• Use sender attachments for static supporting documents.
• Use recipient attachments when you must collect files.
• Choose private when collecting personal or sensitive documents.
• Choose shared when all participants need to access the uploaded content.
• Use required sparingly and only when essential to avoid blocking signing unnecessarily.