#2681·documenso

Share QR link that publicly available

Author: FliwCreated Apr 7, 2026Updated Sep 16, 2026
Labelsstatus: backlogged

Feature Description

Hi, I would like to request a feature to generate a public shareable link (e.g., /share/) for documents that have been fully signed/completed.

Currently, it seems that a public share link already exists internally, as it can be accessed via the QR code in the audit log after a document is completed. However, this link is not easily discoverable or accessible through the main UI or API.

This creates a UX and developer experience issue, where:

  • The feature technically exists
  • But is hidden and not directly usable in a standard workflow

Proposed improvements:

  • Expose the share link directly in the document UI once the document is completed
  • Provide a "Copy Share Link" button for quick access
  • Include the share token in the document API response
  • Optionally allow generating/regenerating the share token

Expected behavior:

  • Only available for completed documents
  • Read-only access to the final signed document
  • Token should be secure and non-guessable

Optional enhancements:

  • Expiration / revocation support
  • Access logs for shared link usage
  • QR code generation directly from the UI (instead of only in audit logs)

This would significantly improve usability and make an already existing capability more accessible for real-world use cases.

Use Case

In many workflows, users need to quickly distribute signed documents via a public link.

Currently, since the share link is only accessible via the audit log QR code, it introduces unnecessary friction:

  • Users must open audit logs
  • Locate the QR code
  • Extract the link manually

This is not intuitive and limits automation use cases.

By exposing the share link directly:

  • Users can easily distribute documents
  • Systems can integrate more cleanly
  • QR-based verification becomes straightforward

Example: A university system generates signed documents and needs to embed a QR code for public verification. Currently, this requires manual extraction, whereas it could be automated if the share link were accessible via API/UI.

Proposed Solution

Introduce an explicit and officially supported public sharing mechanism for completed documents by exposing the existing share link functionality.

Implementation details:

  1. Share Token Exposure
  • Ensure each completed document has a share_token (reuse existing token if already generated internally).
  • Include share_token or share_url in document API responses: GET /api/documents/:id
  1. Public Share Endpoint
  • Standardize a public endpoint: GET /share/:token
  • Validate:
    • Document exists
    • Status = completed
  • Return:
    • Read-only document viewer or direct PDF stream
  1. UI Integration
  • Add a "Copy Share Link" button in the document detail page (visible only when completed)
  • Optionally display QR code directly in the UI (not فقط in audit log)
  1. Token Management (Optional but recommended)
  • Allow regenerating share token (invalidate old link)
  • Add optional expiration timestamp
  • Add toggle: enable/disable public access
  1. Security Considerations
  • Use non-guessable tokens (e.g., nanoid / UUID v4)
  • Enforce strict read-only access
  • Prevent access to non-completed documents

This approach leverages existing internal behavior (QR-based share link) and formalizes it into a first-class feature.

Alternatives (optional)

No response

Additional Context

Image

this is the QR that can be shared publicly, however it still need to get into audit log, and then scan the QR and then share it.

Image

this is the shared document, i just need the URL of the link that i can share to other publicly.

Please check the boxes that apply to this feature request.

  • I have searched the existing feature requests to make sure this is not a duplicate.
  • I have provided a detailed description of the requested feature.
  • I have explained the use case or scenario for this feature.
  • I have included any relevant technical details or design suggestions.
  • I understand that this is a suggestion and that there is no guarantee of implementation.
  • I want to work on creating a PR for this issue if approved