What changed in Docshark this summer

The setup wizard asks about solo or team use, the work you plan to do, and who needs access. After creating a workspace, you can choose a practice mission for sharing, signing, or data rooms. Missions use sample content, save progress between visits, and point to the relevant controls on screen. The setup also handles team invitations when seats are available. Eligible workspaces can start a 14-day Business trial from the dashboard without entering a card at the start.

Docshark Home brings current work into one view: signature requests, unanswered room questions, links nearing expiry, and envelopes with no recent progress. It also shows recent readers and the most-read documents. Each item leads back to the related room, link, or envelope, so an activity signal has a place to act on it.

The library is the starting point for files used in a room, a share link, or an envelope. Upload or import documents, organize them in folders, and select existing files when preparing the next step. Google Drive can be connected for browsing and importing files. Document pickers and larger library lists now page through results, which keeps a growing collection usable without loading every file at once.

A File Request gives someone outside your workspace an upload link to a chosen folder. They can submit files without creating a Docshark account. The owner can ask for an email address or passcode, set an expiry, restrict file types and size, review upload counts, and revoke the link. The uploaded material arrives where the team expects to work with it.

Web Forms handle the information that belongs beside a document: names, answers, dates, and other fields you define. Build a form, publish its link, and review submissions in Docshark. A form can collect details on its own or use a selected agreement template to create an envelope from a submission. That gives intake and signing a shared starting point.

Room creation walks through the name and purpose, files and folders, access rules, and launch details. A visitor preview shows the room before it is shared, and a saved draft can be resumed. Once open, the room has a guest list, groups, and membership controls. Access can also be set for individual files and folders, so a room can contain material for different people without requiring a separate room for each group.

A room can use invited guests and groups, with email or domain rules at entry. Owners can then decide which files and folders each group may open. The room also has access, NDA, and watermark controls. Share links created from room material have their own settings and can carry a customized appearance, so a link's audience and presentation can differ from the room's.

A share link has its own access policy. You can limit viewers, add a password or passcode, set expiry, control downloading and printing, apply a watermark, and revoke access. Link creation can also send the invitation by email. For a protected link, share the password separately. Those choices belong to the link, even when the file also lives inside a room with different defaults.

Read Proof and room analytics show opens over time, unique viewers, time spent, return visits, page attention, and recent readers. Device and region summaries add context. Session replay reconstructs a page-by-page reading path from recorded viewing events. Activity can be exported as raw CSV or a PDF report.

Agreement templates let a team prepare once and use the same structure again. You can start from a template, edit placeholders, inspect version history, and compare revisions. Word documents can supply the source for a template or envelope. The builder carries signing fields and their options, including defaults, validation, visibility, linked fields, and calculations, through to the agreement the recipient sees.

To send an agreement, choose the document or template, add recipients, assign their roles, set the signing order, place fields, and review the envelope. A room document can enter the same signing flow. Draft envelopes can go through internal approval first, with reviewers acting in sequence or together. Reviewers can approve or reject with a note, and their inbox supports decisions across multiple requests.

Members can open pending signature requests in the embedded signing view. Signers can work through fields on a phone and return to unfinished work after a reload. The envelope and room views show recipient progress and document activity as they change. Senders also have manual reminder controls for follow-up. When everyone has finished, the completed PDF and its certificate are available to view or download, with an audit record of the signing steps.

Power Forms turn a ready agreement template into a reusable signing link. The creator sets its public title, description, and appearance, previews the page, and publishes or pauses it. Each visitor enters their own name and email and signs a separate agreement. The template stays the common source while each response has its own envelope and signing record.

An agreement can create work after the first envelope. Agreement Actions link a source-envelope event to a follow-on envelope built from a selected template; owners map signer roles, preview a matching case, and enable or pause the rule. Post-sign obligations track a deliverable or renewal against its source envelope, with an owner, due date, status, and snooze control. The signed file remains connected to the work that follows it.

Workspace members, invitations, and roles are managed in the team area. Google Drive import connects outside files to the Docshark library. Webhooks can be configured for selected events, with a delivery history for checking what was sent. These controls sit beside the document workflows, so the people handling a room or agreement can use the same workspace settings.

Explore the workflows behind this update in the Docshark docs: data rooms, Read Proof, file requests, and signatures. The guide to tracking who read a PDF explains the reading signals in more detail.