When you send a request, your contact receives a link to a simple, no-login page scoped to just their request.
What they can do there
- View the checklist of documents you've asked for, with clear labels for what's still needed.
- Upload files directly, by drag-and-drop or file picker.
- Capture a document with their phone camera instead of scanning it.
- Upload additional documents you didn't explicitly ask for, if relevant.
- Send you a message back through the portal if they have a question. It shows up in the request's activity log on your side.
- Mark an item as not applicable to them, if your checklist allows it.
Why there's no login
The portal link is unique to the request. Your contact doesn't create an account, set a password, or install anything. The link itself is the credential, which is why it's worth treating like one — see below.
This tradeoff is deliberate. Asking a client to create an account is the single most common reason document collection stalls, and every abandoned signup is a document you don't get.
Link handling
- The link goes to the email address on the contact record, so keep that accurate.
- Each request gets its own link. Sending a new request doesn't reuse the old one.
- If a client forwards their link to someone else, that person can see and upload to the request. Treat it the way you'd treat a shared document link.
Branding
Organizations can brand the portal footer so it reads as coming from your firm rather than from docEvault. Your contact still sees that the portal is operated by docEvault on your behalf.
Pointing clients at help
If a contact is stuck, Uploading documents to a request is written for them rather than for you, and you can send it directly.