Per-case collaborators
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.
Last updated
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.
What you need
- A case to share
- The collaborator's email
- The set of file categories they should see
Worker vs Client at the case level
| Panel | Who they are | Where they sign in | Activity verb on add |
|---|---|---|---|
| Team | A workspace member with the Worker role | / | "Riley was assigned to this case" |
| Clients | An external person with the Client role | /portal | "vendor@example.com was given client access to this case" |
The two panels are peers — neither implies a redirect to the other surface. The same email address can be a Worker in your workspace and a Client in someone else's; they're independent.
Step by step
- Open the case in the dashboard.
- Pick the right panel:
- Team — click the person-plus icon, enter the worker's email, pick visible categories, click Assign.
- Clients — click the send icon, enter the client's email (e.g.
vendor@example.com), pick visible categories, click Send.
- The collaborator now appears as a row — avatar, name, and a
⋯menu to Edit visibility, Remove, or (for clients only) Manage forms.
Adding either a worker or a client triggers a real email sent directly from Document Blueprint with a portal sign-in link — this is one of the few places the product sends mail on your behalf instead of composing a draft. The body is templated ("a team member" vs "a client" is the only difference). See How notifications work for the full picture of when emails leave the product vs. stay in-app.