Simply Sign FAQs
Straight answers to the questions legal, compliance, privacy, and operations teams ask before they approve enterprise signing.
Is Simply Sign a SaaS e-signature service?
No. Simply Sign is designed for customer-hosted deployment so documents, audit data, and lifecycle controls remain inside the customer’s governed platform boundary.
Can we use Simply Sign for standalone workflows and case-linked approvals?
Yes. Teams can create standalone envelopes for day-to-day signing or launch signing directly from a case so the document, recipients, activity, artifacts, and audit trail stay attached to the matter.
Can fields be placed directly on the source PDF?
Yes. Users can upload a PDF, preview it immediately, and place signature, initials, date, text, checkbox, and name fields visually on the source document.
How do templates help repeat workflows?
Templates can preserve recipients, routing, field layouts, anchor rules, message copy, expiry settings, and source document blueprints so common workflows can be reused instead of rebuilt.
Do external signers need a platform login?
No. Recipients receive a secure public signing link and can authenticate with passkeys or one-time passcodes without needing a platform account.
What signer actions are captured?
Authentication events, recipient actions, send and delivery history, completion steps, and lifecycle changes are all recorded as part of the evidence trail.
What evidence does Simply Sign generate?
Simply Sign generates a final signed PDF, a structured evidence package, a certificate-style summary, and a unified audit trail covering provenance, timestamps, recipient actions, authentication, and completion history.
Why is Simply Sign materially different from mainstream cloud signing tools?
The key difference is control. Sensitive documents, agreements, approvals, and evidence records stay within the customer’s environment rather than being moved into a third-party SaaS signing silo.