Collaboration and sharing
Comments, reactions and sharing by link
How do you keep a record of who saw a document?
The problem
The conversation about a document should not need its own thread
The conversation and the file live apart
A question about a document turns into a reply-all thread where the file itself is an attachment three messages back, and the answer is a fourth message nobody reads in order.
No record of who actually looked
You send a document and have no way to know, later, whether it was opened, by whom, or when — only that an email left your outbox.
Feedback gets scattered across channels
One comment lands in email, another in WhatsApp, a third is said out loud on a call — none of them attached to the document they are about.
What this is
Comments and reactions attached to the file, not a separate thread about it
Built and available now.
- A comment on a document, visible to anyone who can see that document
- Replies that stay nested under the comment they answer
- A lightweight reaction, for the times a full comment is more than the moment needs
- Everything attached to the file itself, so it travels with the document rather than a mail thread
Sharing and records
A link that expires, and a record of what your contacts opened
Sharing, comments and the activity feed are built. Browsing or exporting the view record is not.
Sharing by link
Available nowSend a document as a link that expires, either open to anyone holding it or restricted to email addresses you name.
Activity feed
Available nowOne chronological record of what happened in a workspace.
Full audit trail
Coming soonDocument opens by contacts, team members and share-link visitors are recorded, but cannot yet be viewed or exported in the product. A way to browse and export them, and a complete, tamper-proof audit trail, are still to be built.
Questions
What people ask about collaboration
How do you keep a record of who saw a document?
Partly. Each time a document is opened, by a contact in their own portal, a team member or someone using a share link, docivault records the document, the time and who opened it (a share-link visit is anonymous and tied to the link). A workspace-wide activity feed records what happened across the workspace. What does not exist yet is any screen to browse those records, any export, or a complete, tamper-proof audit trail.
Where do comments on a document live?
Directly on the document, as threaded comments with replies and reactions, so the conversation about a file stays attached to it instead of splitting off into a separate mail thread where the file is only an attachment. This is built and available now.
Is any of this built today?
Yes, most of it. Comments, replies and reactions on a document are built and available now, as is the workspace activity feed. The part still missing is the audit trail itself: a screen to browse and export the record of who opened a document, and a complete, tamper-proof log.
What is true about access records today?
docivault enforces who can see a document through roles and access scoping, and it records each time a document is opened, whether by a contact in their portal, a team member or a share-link visitor. It does not yet let anyone browse or export those records, and it makes no claim that they form a complete, provable access log. If you need that, it is the piece still to be built.
Put the conversation next to the document
Send a document as a link that expires, either open to anyone holding it or restricted to email addresses you name. Comments, reactions and the activity feed are built too, on top of the roles and access scoping that decide who can see a document in the first place.
- No credit card
- Free plan, no expiry
- The people you exchange with are free