Electronic signatures & audit trails
for Jira
Electronic signatures that prove exactly what was signed, when, and by whom. Designed to support 21 CFR Part 11 · EU Annex 11 · eIDAS · GDPR.
Designed for regulated industries
Electronic signatures and audit trails designed for regulated environments
21 CFR Part 11
FDA — two-component signing, signer affirmation, tamper-evident audit trails, electronic records
EU Annex 11
GMP — hash chain integrity, HMAC sealing, data integrity verification, append-only audit log
eIDAS
EU — simple electronic signatures per Art. 3(10), with optional controls partially aligned to Art. 26. Not an AES or QES provider — see compliance mapping
GDPR
EU — privacy-safe audit trails, GDPR erasure (anonymize display data, preserve hash integrity)
Designed for quality managers, regulatory affairs teams, and compliance officers in pharma, medtech, automotive, and aerospace.
SealDoc is designed for internal document control and approval workflows. It is not a replacement for external-party contract signing services (e.g. DocuSign, Adobe Sign) or notarization.
Signing & compliance
The controls your auditor expects — built in, not bolted on
Electronic Signatures
Multi-person sign-off with meaning (Approved, Reviewed, Verified, Witnessed, Authored, Acknowledged). Signer identity, comment, and timestamp on every signature.
Signing PIN
21 CFR Part 11 two-component signing: your Jira identity plus a personal PIN that only you know. Built-in lockout and expiry policies keep credentials secure.
Approval Workflow
Draft → In Review → Approved state machine. Configurable minimum signers quorum. Submit, approve, or reject with comments.
Revert on Edit
Auto-revoke all signatures when signed content changes. Prevents stale approvals on modified documents.
Content Hash Integrity
Cryptographic hash of document content captured at signing time. Proves exactly what was signed — any later change is immediately detectable.
Chain Sealing
Periodic cryptographic checkpoint of the entire audit chain. Automatically seals after every write and on an hourly schedule. Detects retroactive tampering even if individual entries are recomputed.
Audit & safety
Tamper-evident records, safety classification, and privacy controls
Tamper-Evident Audit Trail
Tamper-evident, insert-only log of every sign, approve, reject, revoke, classify, and configure action. Hash-chained entries with gap detection.
Safety Classification
ASIL (ISO 26262), DAL (DO-178C), Risk Class (IEC 62304), or custom schemes. Per-class approval rules with minimum signers.
Separation of Duties
Submitter ≠ approver. Configurable person-level or department-level independence, enforced at approval time when enabled.
Batch Signing
Sign multiple Jira issues in a single ceremony. Same PIN verification, same affirmation — applied to all selected items.
Confluence Signing
Sign Confluence pages with the same ceremony. Content hash captures page body at time of signing.
GDPR Erasure
Anonymize signer display names while preserving hash chain integrity. Compliant data erasure without breaking the audit trail.
How SealDoc compares
Document signing with hash-chained audit trails — built on Atlassian Forge
Based on publicly available feature lists of Atlassian Marketplace e-signature apps as of March 2026. Individual apps may have added features since this comparison was created.
| Feature | Typical Connect-based e-signature apps | SealDoc |
|---|---|---|
| Basic electronic signatures | ||
| External-party / contract signing | ||
| Runs on Atlassian Forge (no external servers) | ||
| Two-component signing (session + PIN) | ||
| Hash-chained audit trail | ||
| Periodic HMAC sealing | ||
| Safety classification (ASIL / DAL / Risk Class) | ||
| Confluence page signing | ||
| Batch signing |
Get started in 3 steps
From install to your first signed document in minutes
Install from Marketplace
Add SealDoc from the Atlassian Marketplace. It runs on Forge — no external servers or configuration needed.
Set up your signing PIN
Open SealDoc from any Jira issue sidebar. Create your personal signing PIN — the second identification component for 21 CFR Part 11 compliance.
Sign your first document
Choose your intent (Approved, Reviewed, Verified), affirm your identity, and enter your PIN. Your signature is recorded in the tamper-evident audit trail.
Pricing
SealDoc is available on the Atlassian Marketplace with per-user monthly pricing. See the Marketplace listing for current rates, free trial availability, and volume discounts.
Have questions? Read the FAQ — covering eIDAS signature levels, regulatory scope, data handling, and more.