Controlled document workflows for organizations
MySafe is for a partner or legal operations lead in a small firm, and for legal, compliance, and security-sensitive teams, when the wrong version or the wrong reader is expensive. Each document keeps a version history, owner-controlled access, a bounded review request, and an activity trail inside one organization’s workspace.
Access is invite-based: request → review → invitation. There is no self-serve signup.
Available
A document creator or editor can request a controlled link to the current version, a different owner or admin account can approve it, and the link can be issued and later revoked.
Demo
The workflow demo page has a recorded walkthrough and a simulation that runs in your browser, both with synthetic data. Neither runs a real approval.
Planned
A policy a team can change, and approval by more than one approver, with escalation or delegation.
The illustration shows one document, Engagement Letter — Example Client Matter:
Why teams look for control
Version ambiguity
In MySafe: Every upload after the first becomes a numbered version with an optional change note. The document details page marks exactly one version as Current; earlier versions stay listed as Historical and can still be downloaded.
Unclear access
In MySafe: Documents sit inside one organization’s workspace and are not visible to other organizations. Organization membership alone does not open a document: the owner grants read access to a named, registered user and can revoke it.
Weak audit visibility
In MySafe: Uploads, new versions, access grants and revocations, review requests and responses, and archive changes are recorded as activity on the document and shown on the organization’s read-only Audit page.
How it works
Each step is an explicit action by someone in your team. MySafe records it; it does not automate the sequence or route work on its own.
Create a document in your organization workspace, then upload each revision as a new version instead of overwriting the file.
Recorded as
The document owner grants read access to a registered user by email and revokes it when the need ends. Access changes lock once a document is archived.
Recorded as
Ask someone who already has read access to record a decision: reviewed or changes requested, with an optional note. It is a single review request, not a multi-stage approval chain.
Recorded as
Archive a document when it is no longer active. It stays readable, new versions are blocked until it is unarchived, and its recorded activity remains available.
Recorded as
Controlled links
This is the sharing path inside a signed-in organization. It is separate from Action control, which only records a decision, and from the bounded review request above, which records reviewed or changes requested.
The document creator, or someone with permission to upload a new version, requests view or download. The server pins the version that is current at that moment. There is no control to pick an older version, and the form does not take a recipient email. Sending the request does not create the link. The document must be active, and the organization needs another active owner or admin. A blank expiry becomes 7 days, and it cannot be more than 30 days.
A different organization owner or admin account approves or rejects the request. The requester cannot approve their own request. MySafe checks that the approving account is different; it does not verify that a different person is using it. Approval does not create the link.
After approval, the requester or an owner or admin creates the link as a separate step. The address is shown once. Anyone who has it can open it until it expires or is revoked. MySafe does not check who the recipient is. If a newer version becomes current, that link stops working.
An organization owner or admin, or the original requester if they can still upload versions, can revoke an active link. Revoke stops further use. The old address is not shown again. A replacement link needs a new approved request.
Action control
Action control is a different screen. A signed-in member proposes send, share, or approve, and MySafe records one outcome from the fixed policy dac.default, version 1. Teams cannot edit that policy. The recorded decision does not send, share, or approve the document, and it does not replace Controlled links.
The fixed policy permits the proposed action. Allow on approve does not change the document. Allow on send or share is recorded only when a valid approval was already present.
The action is not permitted. The check stops on the first failing reason: the document or version is unavailable, the organization does not match, the person is not allowed, the version is not current, the version is not in an approved state, or the policy is not the fixed one.
The check records that human approval is required. This screen does not grant that approval and does not create a link. The approval that releases a controlled link is the Controlled links step above.
Suitable for a first pilot
Engagement letters or standard agreements where you need to know which version is current and who reviewed it.
Documents with one accountable owner, periodic revisions, and a need to archive what has been superseded.
Material that only named people should open, with read access you grant and revoke per document.
A real document-control problem, a limited initial scope, a team comfortable with a guided pilot reviewed by the MySafe team, and a goal of workflow validation rather than broad rollout.
Not sure you fit yet? Take the document workflow survey or request a written workflow screening.
Trust and scope
MySafe is a controlled document workflow product for organizations. It is not a full document management system, and its claims are intentionally narrow.
Research
Two optional forms for teams that want to share where document work breaks down. Neither is required to request access.
Research survey
We are mapping how UK legal and healthcare teams handle sensitive documents — where work becomes slow, fragmented, or hard to control. This is discovery research, not a sales questionnaire. Estimated time: 4–6 minutes.
Please do not include confidential client, patient, or case-specific information.
Workflow screening
This short form helps us understand whether your team has document-version, approval, access, or audit problems worth discussing.
Please do not include confidential client information or patient-identifiable details in this form.
Prefer email?
Contact us at info@mysafeflow.com
Pilot expectations
Access is invite-based. Submit a request, we review it, and if it is a fit we send an onboarding invitation. Public self-registration is not available. Existing users can sign in.
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.
Invite-based access, organization creation, document upload, version history, archive and soft delete, access grant and revoke, bounded review requests, controlled links with approval by a different owner or admin account, document detail, and audit visibility are part of the current baseline.
Full matter or pack management UI, broad migration tooling, deep third-party integrations, enterprise records management, and open self-serve signup should not be assumed at the current stage.
A limited initial scope, guided by the MySafe team, aimed at validating one real document workflow from invitation and organization setup through upload, versions, access, review, and audit. Pilots use synthetic or public documents. A client's real documents are used only after MySafe's readiness review for real data is complete and MySafe has confirmed in writing for that pilot. That review includes backup and restore, data deletion, monitoring, account protection, an independent security review, incident procedures, and legal review of the privacy notice and pilot terms. It is not complete yet, and we do not give a date for it. The product does not block uploads, so please do not upload real documents until you have that written confirmation. View pilot path
A short description of your organization and the workflow you want to validate. No confidential client details are required for screening or access requests.
Request access
Public self-registration is not available. Access is request → review → invitation: we review each request and, if suitable, send an onboarding invitation.
Written contact is always available
Prefer written contact? Email info@mysafeflow.com or copy the address below. If your browser does not open email automatically, send a message manually.