Sharing & Collaboration

Sharing happens in two places — workspace membership for your team, and the portal for external clients. Both scope by file category: people see only the categories you grant on each case.

Sharing a case creates a real Gmail draft in your own Gmail mailbox with subject, body, and attachments pre-filled. The draft opens in Gmail's compose view in a new tab — you review and click Send from inside Gmail yourself. Document Blueprint never sends mail; it only drafts.

The portal at /portal is where Clients sign in to see cases shared with them. They see only the cases they were added to, only the file categories granted, and any forms exposed for them to fill.

Workspace seats are one of four roles: Owner, Member, Worker, or Client. Owner and Member can manage the team and edit cases; Worker can work cases (and can be scoped); Client is external and only sees the portal.

Invite teammates from Settings → Account → Team. The role picker offers Worker or Member; the invite emails them a sign-in link, and they join on first sign-in.

Workers can be scoped two ways — to a subset of cases (Assigned cases only on their member profile), and within each assigned case to a subset of file categories (set when assigning). Both are enforced server-side.

Each case has two collaborator panels — Team for workspace workers, Clients for external portal users. Add either inline; scope is the list of file categories they can see on this case.

A send template is a saved configuration for a case share — a name, a tokenized subject, a default body, and per-category source rules (which files attach vs. just link). Build them once, reuse on every share.

Document Blueprint communicates outward in three different ways — a Gmail draft we create in your own mailbox that you review and send yourself, an actual email we send for invites and billing, and an in-app bell-icon notification that never leaves the app. Knowing which is which prevents the surprise of "they should have gotten an email by now."