The two layers
Workspace roles decide what someone can do across the workspace — invite people, change billing, manage settings, edit content in general. Every workspace member has exactly one role. Per-entity privacy decides who can read or edit a specific note or collection. The default is “everyone in the workspace can see it”; you can override that on individual items. Both layers run on every request — the answer Bower gives is the most restrictive of the two.Workspace roles
When you invite someone, you pick their role. Owner, Admin, and Member are paid seats; Guest is a free seat with a per-tier cap. Permissions cascade — Owner has everything Admin has, Admin has everything Member has.
¹ Between Member and Admin. Nobody can be made Owner by a role change: the Owner changes only through Transfer ownership.
² A guest can ask Bower to search, summarize and answer questions about the workspace. Bower won’t create or change anything for a guest, and says so when asked to.
Why these roles
- Owner (paid): the workspace lead and billing owner: invoices and billing emails go to them. The only person who can transfer ownership, and provides admin oversight of team work. Cannot read content marked Just me.
- Admin (paid): manages members, settings, and billing. Useful for delegating workspace administration to lab managers; ownership, and with it the billing relationship, stays with the Owner.
- Member (paid): the default for invited collaborators. Can read and edit anything that’s not restricted away from them, and create new content.
- Guest (free): read-only across the workspace, no seat cost. Unlimited on every plan. Right for external collaborators and stakeholders who need visibility but don’t warrant a paid seat.
Paid ↔ Guest is a billing-class change
Moving a user between the paid roles (Owner / Admin / Member) and Guest isn’t a role flip — it’s remove and re-invite. The role dropdown deliberately doesn’t offer Guest for paid members, and doesn’t offer paid roles for guests. See Invite team members for why.Last-Owner protection
A workspace must always have at least one Owner. If you try to:- Demote the only Owner to Admin (or anything else), or
- Remove the only Owner from the workspace (including leaving the workspace yourself if you’re the sole Owner),
Per-entity privacy
By default, every note and collection in a workspace is visible to all members — that’s “Anyone in this workspace” mode. You can override this on individual items via the Share dialog. There are three modes:
For the full Share dialog walkthrough, see Sharing notes and collections.
How the two layers interact
When someone tries to read a note, Bower checks both layers and returns the most restrictive answer:- Workspace role decides if they can read content at all. Guests can read but not edit; non-members can’t read anything.
- Entity privacy decides if they can read this specific note. A note in Only specific people mode is invisible to anyone not on the list (or who isn’t the creator or workspace Owner). A note in Just me mode is invisible to anyone except the creator and people the creator has explicitly added.
- Workspace Member opens a default-public note → reads it (workspace role allows, entity is open).
- Workspace Member opens a Only specific people note they’re not on → 404. They don’t get to know it exists.
- Workspace Owner opens a Only specific people note → reads it (Owner has admin oversight in this mode).
- Workspace Owner opens a Just me note someone else created → 404. Owner has no oversight on Just-me content.
- Workspace Guest opens a default-public note → reads it (the role can read, entity is open). They cannot edit (read-only role blocks).
Special people: creator and Owner
Two people always retain a baseline level of access:- The entity creator — whoever made the note or collection always retains Full (Manage) access on it. You can mark your own work Only specific people without locking yourself out.
- The workspace Owner — retains access on Workspace and Only specific people entities (admin oversight). The Owner does not retain access on Just me entities — that’s the structural difference that makes “Just me” actually private.
When the creator leaves the workspace
If someone is removed from a workspace, or deletes their Bower account, the Just me notes and collections they created in that workspace are not deleted and do not become unreachable. Each one is handed to the workspace Owner (or, if the workspace has no Owner, to its first Admin) and switched to Only specific people.- The workspace Owner can then read, manage, or delete them.
- Anyone the creator had already added to the list keeps their access.
- Nobody else gains access. Other members still can’t see them.
Restricted content the user can’t see
When a workspace member follows a direct link to a note or collection they don’t have access to, Bower shows a calm splash page that:- Confirms the content is private (not deleted).
- Shows the owner’s name and email so the user knows who to ask.
- Offers a Request access button that opens an email pre-filled with a polite request.
Compliance: disable “Just me” for the whole workspace
For regulated industries (HIPAA, IRB-governed research, audit-everything environments), the workspace Owner can disable Just me mode entirely. When Just me is disabled in the workspace:- Users clicking “Just me” in the Share dialog get a Only specific people entity with themselves on the list (workspace Owner still has access).
- The auto-demotion from Only specific people back to Just me doesn’t fire when the last collaborator is removed.
- The behavior falls back to the previous Bower model — every entity is readable by the workspace Owner.
Audit log
Every privacy-mode change and access-list change is recorded in the audit log:- Who made the change.
- What changed (mode flip, grant added, grant revoked).
- When it happened.
- What entity it affected.