LibreSign / LibreSign/libresign

[FEATURE]: signing module for multiple documents

Open
#5,762 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request
Dominant language
PHP
Stars
818
Forks
146
Avg merge
11h 31m
Merged PRs (30d)
326

Description

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like

Title: signing module for multiple documents

Description:
Summary
Implement a batch signing feature that allows users to sign multiple documents with a single command, improving efficiency when dealing with multiple files that require the same signature.
Problem Statement
Currently, users need to sign documents one by one, which can be time-consuming and inefficient when dealing with multiple documents that require the same signature or approval process.

Proposed Solution
Add a batch signing module that enables users to:

Select multiple contacts for signing
Apply the same signature to all selected documents in one action
Review a summary of documents to be signed before confirming
Receive feedback on the batch signing operation (success/failure per document)

Expected Benefits

Time savings: Significantly reduce the time needed to sign multiple documents
Improved UX: Better user experience for bulk operations
Productivity: Streamline workflows that require signing multiple related documents

Suggested Implementation Details

  • UI for multi-contacts selection
  • Batch processing queue
  • Progress indicator for batch operations
  • Error handling for individual document failures
  • Summary report of batch signing results
  • Option to continue on error or stop on first failure

Use Cases

Signing multiple contracts from the same client
Approving multiple internal documents
Processing bulk administrative documents

Describe alternatives you've considered

The user imports a list in CSV format with predefined fields such as name and email.

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified in the issue. Start by locating the existing document-signing flow and its UI, then define the batch workflow, failure handling, progress feedback, and completion criteria before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.