Repository navigation
SignuDoc 0.3.0
Sign-in security and audit features for organizations that need them, and two new ways to fix a sent envelope. This release changes the database: see the end of this entry.
Envelopes
- A sender can correct a signer's email address after sending. The old signing link stops working, the new address gets a fresh invitation, and the audit trail records the correction.
- A finished envelope can be copied into a new draft with the same document, recipients and fields, and nothing that was filled in.
Sign-in security
- Two-step sign-in: anyone with an account can add an authenticator app under Settings, with ten single-use backup codes. Signing in then asks for a code after the password.
- Administrators can require two-step sign-in of everyone (Settings, Organization, Sign-in security), and reset it for someone who lost their phone (People).
- Session limits: administrators can sign people out after a time without use (15 minutes to 8 hours) and at the latest a set time after sign-in (8 hours to 3 days). Anyone can sign out on every device at once.
- A session that was ended (signed out everywhere, or reset by an administrator) stops working at once, not when the short-lived session cookie runs out.
- Ten wrong passwords for one email address within 15 minutes stop sign-in for that address for 15 minutes.
- The site audit trail now records sign-ins, failed sign-ins, lockouts, sign-outs, password changes and resets, two-step sign-in changes, logo changes and the email domain being added. It moved from the Part 11 panel to the new Sign-in security panel, and is there whether or not Part 11 mode is on.
- Single sign-on over OpenID Connect (Okta, Microsoft Entra ID, Google Workspace and others), set up with
SSO_ISSUER,SSO_CLIENT_IDandSSO_CLIENT_SECRET. New people get an account under the install's sign-up rule.PASSWORD_SIGN_IN=offthen turns password sign-in off, except for the addresses inPASSWORD_SIGN_IN_ALLOWED_EMAILS. - Audit rows (site and document trails) and security events are written to the function logs as JSON lines once saved, so a Vercel log drain can deliver them to a SIEM.
AUDIT_LOG=offstops the audit lines. - A daily backup of the database and files to a second, private Blob store, turned on with
BACKUP_BLOB_READ_WRITE_TOKEN, andnpm run restore-backupto restore it into a new database and store. Seedocs/backup-and-restore.md.vercel.jsonhas a second daily cron job, which does nothing until the token is set. - Account closure requests and account deletions are recorded in the site audit trail.
docs/soc2: a SOC 2 pack for organizations that put an install in their audit: a control map to the Trust Services Criteria, vendor duties, questionnaire answers and sample policies.
Project security
- CodeQL, dependency review, a weekly
npm auditand OpenSSF Scorecard run on the SignuDoc repository (skipped in a copy made by the Deploy button). - Each release gets a CycloneDX SBOM, a source archive and signed build provenance attached.
SECURITY.mdsays how to verify them.
This release changes the database (20261115100000_copied_audit_event.sql, 20261116100000_signer_corrected.sql, 20261117090000_sign_in_security.sql, 20261117100000_session_controls.sql). On Vercel the production build applies them, so nothing is needed by hand. On other hosts, run npm run db:migrate as on every deploy.
Full changelog: CHANGELOG.md