BopSuite is built for small firms — typically 1–15 professionals. Here's how to bring your team in.
Invite a team member
- Sidebar → Settings
- Tab → Team
- Click Invite member
- Enter their email + pick a role (see below)
- Send
They'll receive an email with a magic link. Clicking it lands them on a simplified signup form (name + password only — no industry selection or org-creation, since they're joining yours).
After they accept, they're a member of your org. Their dashboard shows the same matters, clients, and templates you do.
Roles
Three roles, in increasing power:
- Member — Can see and edit matters, clients, doc requests, calendar, etc. Can't change billing, can't invite, can't delete the org.
- Admin — Member + can invite/remove other team members and edit org settings.
- Owner — Admin + billing + delete-the-org. Usually just the founder. Set automatically on the user who signed up.
Roles are org-scoped — a user is exactly one role inside one org. To collaborate across orgs (e.g., co-counsel arrangement), they'd need separate accounts.
Plan limits on team size
| Tier | Team size |
|---|---|
| Starter | 1 user |
| Practice | Up to 3 users |
| Firm | Up to 10 users |
Going over the limit blocks new invites until you upgrade or remove a member.
Assigning work
Each matter can have one responsible user (the lead attorney/CPA on the matter). Set it when creating the matter or change it from the Edit panel.
Each task can have one assignee. When you apply a workflow, the steps marked default_role: 'self' auto-assign to whoever applied it; others come in unassigned and you assign manually.
Removing a member
Settings → Team → click into the member → Remove from team.
They lose access immediately. Their historical actions in activity_log stay attributed to their email address even after they're gone.
What about clients?
Clients aren't team members. They access their stuff via magic-link emails (doc-request portal, signed-document download, invoice-payment page) — never with a real account. That keeps your org membership tight and avoids accidentally giving clients access to internal notes.
If a client needs an account-level relationship (e.g., a recurring tax client who logs in monthly to update their books), the cleanest path right now is for them to sign up for their own BopSuite org — different product, different relationship. That's a v2 design problem we haven't solved yet.