Skip to content
docivault

Collaboration and sharing

Comments, reactions and sharing by link

How do you keep a record of who saw a document?

Comments, replies and reactions sit directly on the document, so the conversation about it never splits off into a separate mail thread. That is built and available now. A complete record of every view and download by every reader is not — today a contact opening a document in their portal is recorded, and a colleague or share-link visitor is not.
Available now

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. The complete view-and-download log is not.

  • Sharing by link

    Available now

    Send a document as a link that expires, either open to anyone holding it or restricted to email addresses you name.

  • Activity feed

    Available now

    One chronological record of what happened in a workspace.

  • Full audit trail

    Coming soon

    A complete record of every view and every download against a document, whoever opened it and however they reached it.

Questions

What people ask about collaboration

How do you keep a record of who saw a document?

Partly. When one of your contacts opens or downloads a document in their own portal, that is recorded against the document. A workspace-wide activity feed records what happened across the workspace. What does not exist yet is a single complete log of every view and every download by everyone — a colleague opening a file, or someone opening a share link, is not recorded that way.

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 complete audit trail — a record of every view and download by every kind of user, in one place.

What is true about access records today?

docivault enforces who can see a document through roles and access scoping, and it records when a contact opens or downloads something through their portal. It does not yet record a team member opening a document, or a visitor opening a share link. If you need a complete, provable access log for every reader, that 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