Skip to content

[Feature request] Resume Incomplete Submissions via Email or other Identifier #632

Description

@Voxel07

Problem Statement

I'm using self-hosted DocuSeal and have a use case where recipients need to sign documents incrementally over time. Currently, each time a recipient clicks the invitation link, a new submission is created, rather than resuming their existing incomplete submission.

Use Case

  • Document Type: Confirmation of receipt for multiple items
  • Distribution: Single invitation link shared with ~50 people
  • Workflow: Items are distributed gradually over time, not all at once
  • Current Issue: Recipients must complete all signatures in one session, or multiple submissions are created

Proposed Solution

Enable recipients to resume incomplete submissions using a unique identifier:

flowchart TD
    A[Recipient clicks invitation link] --> B[Enter unique identifier]
    B --> C{Existing incomplete<br/>submission found?}
    C -->|Yes| D[Resume existing submission]
    C -->|No| E[Create new submission]
    D --> F[Sign received items]
    E --> F
    F --> G[Save and close]
    G --> H[Return later to sign<br/>additional items]
    H --> A
Loading

Benefits

  • Eliminates need for custom API integration
  • Maintains single submission per recipient
  • Supports incremental signing workflow
  • Improves user experience for long-running processes

Note

The unique identifier doesn't necessarily have to be email. Other fields like name or phone number could be repurposed for this purpose, as long as they can be mapped from the input fields available in the invitation link.

Alternative Considered

This could be achieved via API calls through an external application, but native support would be preferable to avoid additional integration complexity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions