01
Draft uploaded
Northbridge Demo Legal uploads Engagement Letter — Example Client Matter into an organization-scoped documents workspace.
Controlled workflow demo
Controlled document workflow for small legal teams
MySafe is a controlled document workflow — not generic file storage and not a full document management system. This public page shows one synthetic demo lifecycle so you can understand the pilot without registering.
Watch the demo
A recorded walkthrough of controlled sharing for one document version, with synthetic accounts and documents. English captions are part of the video.
You do not need an account to understand the pilot flow. This public page shows the controlled workflow using synthetic demo material. Actual product access is request/review/invite-based.
Request written overview
Email info@mysafeflow.com
If your browser does not open email automatically, copy the address and send a message manually.
Problem
File storage keeps documents. It does not always prove which version was current, who reviewed it, what was sent externally, or what remains active.
Synthetic demo scenario
This page uses synthetic demo material only — not a real client matter and not a live login for visitors. The scenario uses a matter-style document name for clarity; the shipped product path today is organization-scoped documents, versions, access control, review, and audit evidence.
- Demo organization
- Northbridge Demo Legal
- Demo document
- Engagement Letter — Example Client Matter
- Scenario
- Small legal team controls an engagement letter lifecycle
Document access in the demo
The demo is based on a synthetic organization and synthetic documents. In real use, documents are scoped to the organization workspace that uploaded them. Other organizations cannot browse or access those documents.
Access should be granted only to named users or approved workflow participants, for a defined purpose, and reviewed when the workflow changes or ends.
Workflow
One concrete lifecycle for the synthetic engagement letter — not a full approval suite, not a matter-pack management UI, and not open public self-service.
02
Review requested
Review is an explicit handoff recorded in the product — not an informal email attachment thread.
03
Updated version created
Changes create a new version instead of an ambiguous overwrite of the same file.
04
Current version marked
The product can answer which version is current for the document.
05
Access granted for review
Named shared access is visible in the workspace rather than disappearing into an unmanaged inbox trail.
06
Document archived
Lifecycle includes an explicit archived state when the engagement letter is no longer active.
07
Audit/history remains visible
Earlier upload, review, version, and access events stay inspectable after archive.
Simulation on synthetic data. No real documents, links or approvals are created.
Try the controlled link flow
Switch roles and follow one synthetic request from request to revoke. State stays in this browser tab and reloading the page resets it. The simulation does not call the document API and uploads nothing. Each completed step sends only the step name, so we can count steps per day in aggregate. No cookies or identifiers are attached, and nothing that identifies you is stored with the count.
Steps
- 1. Request (current)
- 2. Approve
- 3. Create link
- 4. Open
- 5. Revoke
- 6. Open again
An editor asks to share the version that is current now, v3, for viewing. A blank expiry means 7 days; the maximum is 30.
Expected role: Requester. Acting as: Daniel Okafor (Requester).
State
- Document
- Engagement Letter, synthetic
- Current version
- v3 (v2 is older)
- Request
- Not requested
- Link
- Not created
- Recipient access
- Not opened
History
Nothing recorded yet.
Decision examples
Two short cases for the fixed policy dac.default version 1. Each shows the facts the policy sees and why it decides.
What this shows
- version integrity
- lifecycle state visibility
- review traceability
- access-grant visibility
- audit/history visibility
- organization-scoped access
What it is not
- not generic file storage
- not a full document management system
- not a full matter-pack management UI
- not open public self-service
- not self-serve product access without review
- not a legal compliance guarantee
- not a certification claim
- not legal advice
Access model
Access is request/review/invite-based so early use can stay controlled and properly scoped. Founding Access is invite-only and free: taking part in the pilot costs nothing. Any paid continuation needs a separate written agreement. No card is required, and there is no automatic charge or automatic move to a paid plan.
- Request access
- We review fit before sending an invite
- If suitable, an onboarding invitation is sent
- Onboarding starts with synthetic/demo material first
There is no open public self-service path from this page. Existing users can sign in. Written questions: info@mysafeflow.com.
Request access
If this workflow is relevant, request access for a controlled review. Access is request/review/invite-based. You can also ask for a short written overview first.
Email info@mysafeflow.com
If your browser does not open email automatically, copy the address and send a message manually.
This page is a controlled workflow demo for pilot discussion. It is not an enterprise procurement package, legal compliance guarantee, certification claim, or full matter-pack product UI.