Support
Support
Getting help. Self-serve answers, contacting support, and what to include so we can help fast.
Self-serve first
Most questions answer faster here than in a queue:
- This documentation. Every feature covered end to end; use the search box (it indexes every page).
- The workspace. Home's needs-you queue and each surface's empty states usually tell you what is blocking.
- Verification. For "is this document real" questions, the public verification page answers directly.
Contacting support
Reach us from inside the app. The support entry in Docshark opens a request with your workspace context attached. Outside the app, use the support channel on the Docshark site.
What makes a request fast
Include what lets us find your record without a round trip:
- The envelope or link. The URL or the support reference on the certificate.
- The document name. Or room, or form.
- What you expected vs what happened. Including the exact error text if there was one.
- The recipient's email, for delivery and signing problems (check their spam folder first, signing emails are the most common "it never arrived").
Common quick answers
- "The link says access denied", the viewer hit a gate: wrong password, off the allowlist, expired link, or over the view cap. The link's denied-attempts log shows exactly which, see managing links.
- "The signer says they can't finish". A required field is unfilled; the guided signer walks them through what is left.
- "My upload stalled", large files upload in resumable chunks; reopen the library, the upload usually resumes where it stopped.
- "Where did my analytics go". Retention is plan-based (14–365 days); older activity rolls off. See retention.
Status and incidents
For service disruptions we communicate through the product. If the whole workspace is unreachable, that is an incident on our side. Not your configuration.