Platform · Control · Use
Share & Recall
Give the right person access to a defined task, for a defined period, and end it when the work ends.
Share & Recall covers who can see material, for how long, and how access ends. In our development build, Request details stay with one verified recipient for a defined period and access can be revoked. Working with documents, and recalling access to them, are designed and not yet built. Ending access is real; un-sending is not.
Control is in our development build, for Request details. Use and recall of documents are designed, not yet built.
From the Request record in our development build: who the Request is for, when access ends, and the action that ends it earlier.
The boundary
Ending access is real. Un-sending is not.
Switch between the two states. Only what sits inside DocuPrivé's control changes.
What ending access can reach
Inside DocuPrivé's control
Access ends 14 Oct 2026, 01:57 UTC, or earlier if revoked
Outside it
- A copy already downloaded
- A copy forwarded by email
- Permissions in someone else's system
- A printed page or a screenshot
Unchanged when access ends. Recall cannot reach these.
In our development build
What the recipient sees.
- Only that Request. The recipient sees only that Request: who asked, what is needed and when access ends. They do not join the requesting organization.
- A verified address. Recipient access starts with a verified receiving email address.
- An exact end. Every Request carries the exact date and time its access ends. Access to a Request can be revoked, and the notification can be resent.
External people stay external.
A recipient answers one Request. They do not join the requesting organization, and they do not see its other Rooms, Requests or people.
In our development buildOnly what the task needs.
People work with the documents a task needs, and no more. Access is meant to relate to a task or a Room, not to everything an organization holds.
Designed, not yet builtFiles and links differ.
A file held in DocuPrivé and a link to material held elsewhere are different things, with different controls. A link does not make DocuPrivé responsible for the other system.
Designed, not yet built A file or a link?Questions
4 answers. More on the questions page.
Does the recipient join our organization?
No. The recipient sees only the Request they were asked to answer and does not join the requesting organization. In the development build, access starts with verifying the receiving email address the Request was issued to.
What happens after access ends?
The recipient can no longer open the Request details in DocuPrivé. Anything already copied outside DocuPrivé is beyond its reach.
Can DocuPrivé delete a copy someone downloaded?
No. Recall is designed to end access that DocuPrivé controls. It cannot reach copies already downloaded, or change permissions in someone else's system.
Is sharing a link the same as sharing a file?
No. A file held in DocuPrivé and a link to material held elsewhere are different things, with different controls. A link does not make DocuPrivé responsible for the other system.