Add colleagues to your workspace so they can capture, search, and collaborate on shared notes and collections. Bower invites are a link you copy and share — we don’t email the invitee for you. That’s deliberate: it keeps each invite traceable to a real conversation, lets you pick the channel (email, Slack, WhatsApp, in-person), and avoids triggering inbox-security filters on outreach mail.Documentation Index
Fetch the complete documentation index at: https://docs.bowerlabs.ai/llms.txt
Use this file to discover all available pages before exploring further.
How to invite someone
Open the invite dialog
Click your avatar in the bottom-left and choose Invite member, or go to Settings → Members → Invite member.
Enter the invitee's email and pick a role
The email is what the invite is bound to — the recipient must sign in or sign up with that exact address to accept. Pick Guest (free, read-only) or Paid member (Admin or Member).
Copy the link Bower generates
Bower creates a unique invite link and shows it on the next screen. The link is auto-selected so Cmd+C / Ctrl+C just works. Share it however you like.
Roles
Bower has five workspace roles. Four are paid seats that count toward your subscription; the fifth is a free guest with a per-tier cap.| Role | Billing class | What they can do |
|---|---|---|
| Owner | Paid seat | Everything an Admin can do, plus manage billing and transfer ownership. Every workspace has at least one Owner — the person who created it. Ownership can be transferred to another Admin. |
| Admin | Paid seat | Everything a Member can do, plus invite and remove members, change member roles, edit workspace settings, and manage workspace instructions. Cannot manage billing. |
| Member | Paid seat | Capture, view, edit, and search all notes, protocols, and collections in the workspace. The default for invited collaborators. |
| Viewer | Paid seat | Strict read-only across the workspace — browse and search, but never edit. Designed for paid-seat stakeholders where read-only must be guaranteed by role, not just per-entity restriction (auditors, IRB observers, regulated reviewers). |
| Guest | Free | Read-only across the workspace, no seat cost. Capped by plan. Right for external collaborators, supervisors, and stakeholders who need visibility but don’t warrant a paid seat. |
Viewer vs Guest today. Both Viewer and Guest are read-only right now, so the practical difference is billing: Viewer is a paid seat, Guest is free. The Viewer role is reserved as the strict read-only seat for the day Guest gains some write actions in the workspace — at which point the two roles will visibly diverge. Today the invite dialog surfaces Guest for the read-only case; Viewer assignments are handled by contacting support.
Guest caps per plan
Guests don’t consume a paid seat, but they’re capped by your plan:| Plan | Guest allowance |
|---|---|
| Starter | 1 guest |
| Pro | 4 guests |
| Team | 4 guests per paid seat |
Paid ↔ Guest is “remove and re-invite”, not in-place
Changing a guest into a paid member (or a paid member back to a guest) is a billing-class change, not a role flip. There’s no in-place toggle for it — admins must remove the user and re-invite them in the new class. This is deliberate:- Promoting a guest to paid is a Stripe-billable event that needs an explicit seat purchase, including a prorated-charge preview.
- Demoting a paid member to guest is a cancellation that should be a conscious decision (and may need a seat release).
Pending invites
Open Settings → Members to see invites that haven’t been accepted yet. From there you can:- Copy the link again if the invitee lost it.
- Revoke a pending invite. For a guest, the slot is freed immediately. For a pending paid seat, the seat is released and Stripe issues a prorated credit on your next invoice.
What each role can see
Everyone in a workspace — including Guests — can see content that’s set to Anyone in this workspace privacy mode (the default). Two layers of access control then filter what individual people see beyond that:- Workspace role — Guests are read-only across the board; Members, Admins, and Owners can edit at their role’s level.
- Per-entity privacy — any note or collection can be restricted to Only specific people or Just me. Restricted content is hidden from anyone not on the list, regardless of workspace role.