Sign documents with proof of who signed and when.

Prepare a PDF, assign fields and participants, and follow the signing process. Signing Flows brings the signed document and its recorded evidence together.

Use your browser. Invited signers access their document through a personal link.

Rental agreement.pdf
FILL IN Monthly amount FILL IN Handover date
Signed · evidence recorded

Signers

ALAnna L.Signed
MPMark P.Signed
RSRita S.Their turn

Evidence record

Document opened14:02 · Example event
Identity step recordedConfigured identity method
Signature applied14:07 · TSA stamp
Examples of configurable trust services Barbados TRIDENT EU QTSPs e-IDs in card formats Other identity and signature providers
Document controls

Security, integrity and traceability.

Understand who can access a document, which revision each signature covers, and what evidence records the process.

Controlled access

Account permissions and database access policies control access within the platform. Signing keys and trust services depend on the configured provider and deployment.

Signed revisions

Each digital signature covers a revision of the PDF. Later permitted changes can coexist with valid earlier signatures. Review the signature history and document checks to understand what changed.

Recorded evidence

The evidence record captures events in the platform. PDF certification, timestamping and long-term validation depend on the selected mode, certificates and services; they are not an unconditional guarantee against later changes.

Fill in before signing

Most documents are not just signed: first they have to be filled in.

A promissory note needs the amount. A rental agreement, the handover date. A consent form, the ID number of the person signing it. Sending out an empty PDF and asking people to fill it in by hand before scanning it is exactly the work we came to take off your hands.

  • Each person sees only their part. Fields are assigned to participants for completion. The completed document can contain information supplied by several people.
  • With rules. Configure required fields and validate their values as part of the signing process.
  • And it stays inside the document. Completed values become part of the PDF revision being signed.

Signing path

ALAnna · TenantSigned
MPMark · GuarantorSigned
RSRita · GuarantorTheir turn
JIJames · OwnerWaiting
CCEstate agency · CopyDoes not sign
The proof

Every signature comes with its own evidence record.

Keep the document together with the recorded signing events. The record helps you inspect how the process progressed and what evidence was collected.

  • Chained. Recorded events are linked by hashes so the evidence chain can be checked for changes.
  • Timestamped when configured. An external timestamp provides time evidence when that service is enabled and available.
  • Inspect the signatures. Use a compatible PDF validator to inspect revisions and certificate trust. Results depend on the reader, trust configuration and validation material.

Evidence record · Rental agreement

Flow sent03/04 09:14 · 4 recipients
Document opened03/04 14:02 · Example event
Identity verifiedConfigured certificate provider
Fields filled inAmount · Handover date
Signature appliedPAdES · TSA stamp 03/04 14:07:22Z
Certificate issuedSHA-256 a1f3…9c2e
How it works

Four steps, and the fourth one is done by the system.

Prepare the document, assign the participants and follow the outcome. Use the product tour to explore each step and the available workspaces.

1

Upload the document

A PDF, just as you have it.

2

Mark what each person fills in

Assign the fields that each participant needs to complete.

3

Define the path

In order, all at once, or mixed. With copies for anyone who needs to know without signing.

4

They sign and you get everything

The signed document, the completion certificate and the full evidence record.

Deployment context

One product, configured for your environment.

Start with your workflows, identity systems and deployment requirements. Build a provider catalogue that can grow with your organization.

01

Your organization

Shape the journey around your users, teams and business processes.

02

Your provider ecosystem

Plan the identity providers, credentials and trust services for each deployment.

03

Room to grow

Add new deployment contexts as requirements evolve. Provider availability and connection requirements are reviewed for each integration.

Choosing your setup

Bring the workflow and trust services together.

Evaluate the document journey, integration needs and available trust services as separate parts of your solution.

Workflow requirements

Start with the document journey

  • Identify participants and responsibilities
  • Review field and routing requirements
  • Check the expected document volume
  • Choose appropriate identity steps
  • Plan support and operational ownership
Trust requirements

Choose services for your context

  • Review certificate trust and provider availability
  • Assess timestamp and validation needs
  • Check the intended jurisdictions
  • Understand the document mode and its limits
  • Test the outcome in the target PDF reader
Signing Flows

Coordinate the complete process

  • Prepare documents, fields and participants
  • Use the providers configured for your deployment
  • Follow signing progress and recorded events
  • Integrate documents and workflows through the API
  • Retrieve documents and supporting evidence

The product tour explains the workflow and access points. Available services and deployment requirements are configured for each environment.

Product tour

See the complete signing journey.

Explore the four steps and find the workspace for business teams, individual users, developers or platform operators.

Explore the product tour
Citizen Identity Orchestration

Part of a broader digital journey.

Signing Flows is a building block of Entrust Citizen Identity Orchestration solution.

Explore Entrust CIO

Start with one document.

Create your account, prepare a document and explore the signing process and evidence record.