Skip to content

Generate completion certificates and evidence packages for accepted documents #36

@jusso-dev

Description

@jusso-dev

Context

ScopeStack records audit logs and acceptance metadata, but mature e-signature tools provide a clear completion certificate/evidence package that can be downloaded and retained with the signed document.

Goal

Generate a completion certificate for accepted documents that summarizes signer identity, timestamps, audit events, document version, and integrity details.

Scope

  • Add a downloadable certificate PDF or appended evidence section.
  • Include:
    • Document title/reference/version.
    • Organisation and client.
    • Recipient names/emails/roles.
    • Sent/viewed/accepted/declined timestamps.
    • IP address and user agent for key events where available.
    • Signature type and accepted signature value/image.
    • Completed signer fields once signer fields exist.
    • Audit event timeline.
    • Document hash or rendered PDF hash for integrity.
  • Expose certificate download from document detail and client portal after completion.

UX Notes

  • Label it clearly: "Completion certificate" or "Evidence certificate".
  • Keep the certificate sober and legal/compliance oriented.
  • Include a short explanation that it records the signing and acceptance history.

Data/Architecture Notes

  • Use existing Acceptance, AuditLog, DocumentRecipient, and rendered PDF data.
  • Add a hash utility for final document content/PDF bytes.
  • Consider storing the generated certificate or generating on demand.

Acceptance Criteria

  • Accepted documents have a completion certificate download.
  • Certificate includes signer and event evidence.
  • Certificate includes document version/reference and integrity hash.
  • Certificate generation is covered by tests for required fields.
  • Certificate remains available after document is locked.

Dependencies

  • Signer fields should feed into the certificate when available.
  • Correct/void/reassign events should appear in the certificate timeline.

Priority

P1. Important for trust, compliance, and customer confidence.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions