From a document to a business process.
Show how people prepare work, take their turn and return the result to the organisation. Let the audience see their own process in the journey.
A document is only the beginning.
Start with the business journey: a team needs to prepare an agreement, invite the right people and follow the work through to completion. Signing Flows brings those activities into a shared workflow.
Show
Use the product tour to introduce the journey before opening a workspace.
Say
“Let’s follow one agreement from preparation to the next action in the business process.”
Ask
“Who prepares the document, who participates, and which system needs the outcome?”
Presenter notes
Keep the opening universal. Use a fictional supplier agreement, with all business terms already filled in. Avoid customer names and country-specific promises.
Make the next action clear.
Move into the company workspace. Open a prepared demo document or upload a synthetic PDF. Introduce the participants and explain the order in which you want them to act.
Show
Locate the document, its participants and the workflow configuration. Explain the chosen sequence.
Say
“The sender decides who needs to participate and how the work should progress.”
Ask
“Does your process need a sequence, several participants working in parallel, or an individual copy for each person?”
Presenter notes
Rehearse the exact workflow and account beforehand. Use a simple sequential example as the main story. Keep quorum and separate-copy examples as optional branches, only when prepared and tested.
Show the participant’s experience.
Use an invitation created for a controlled demo recipient. Switch to that person’s browser session, open the document and follow the configured steps. Then return to the sender’s workspace.
Show
The participant’s document and the next action shown by the configured flow.
Say
“Now we are looking at the same process from the participant’s side.”
Ask
“Where should this experience sit: a dedicated journey, or a step within your own application?”
Presenter notes
The sign-in link is a workspace entry point, not a substitute for a recipient invitation. Prepare the invitation separately. Use only demo identities and a rehearsed provider. Do not put tokens, PINs or personal data into this guide or a shared screen.
Bring the outcome back to the team.
Return to the document in the company workspace. Show its current status and the actions available for that particular run. If the run has completed, open its evidence record and available downloads.
Show
The resulting status, the evidence record and the available output files.
Say
“The team can return to the document and see what happened in this workflow.”
Ask
“Which system or team should receive the outcome next?”
Presenter notes
Explain only what this run actually shows. Questions about signature validity, timestamps, evidence integrity or long-term validation belong in the reviewed technical briefing. Do not infer those guarantees from a status badge.
Same product.
A different lens for each audience.
Business & sales
Stay with the four-step story. Explore the handoffs, participants and next business action.
Explore the product tour ↗Solution architects
Continue into the integration demo and API reference. Discuss where the document starts and where the result belongs.
Open integration demo ↗Operations & delivery
Use the operator workspace to discuss the configured environment. Show only a rehearsed view with appropriate access.
Open operator workspace ↗A smooth demo starts before the call.
- Confirm access. Use an approved sandbox account and the right permissions for each workspace.
- Rehearse the complete run. Prepare a synthetic document, demo recipients and a working signing configuration.
- Separate browser sessions. Keep the sender and participant identities visibly distinct.
- Prepare a completed example. If the live flow stops, label the fallback clearly as a previously completed demo.
- Choose the language. The product tour supports English, Spanish and Arabic. Rehearse the platform separately; the Arabic tour does not imply an Arabic signing journey.
- Set up the technical extension. The integration demo needs its own API access. Keep credentials off the shared screen.
When a question goes beyond this demo
Capture the specific provider, configuration and required outcome. Refer questions about signatures, timestamps, evidence or validity to the reviewed technical briefing. Keep certification and card-reader demonstrations out of the core story unless they have been separately prepared and approved.
“Which journey would you connect first?”
Agree on one candidate process, the people involved, the originating system and the desired outcome. Use those four answers to shape a focused follow-up demonstration.
Signing Flows is a building block of the Entrust Citizen Identity Orchestration solution.
About this edition
Internal review draft · 15 September 2026
Prepared for Entrust colleagues. Links open the shared sandbox; workspace access and available behaviour depend on its configuration. This guide is not an account provisioning tool.