Roles and permissions

Your Bookbag account gives everyone in an organization one of four roles: owner, admin, member or viewer. This page says precisely what each can do in Bookbag.

The short version first, because it is genuinely this short.

The rule

Owners, admins and members can do everything to any project in the organization. Viewers can read everything and change nothing.

That is not a summary — it is the entire permission model as implemented. Inside Bookbag, the three writing roles are treated identically. No screen, no button and no endpoint distinguishes an owner from an admin from a member. The only role singled out anywhere is viewer.

Two things sit outside that rule:

• The person who created a project always has full access to it, whatever their role in the organization.
• A platform administrator — a separate thing entirely — can reach any project on the installation.

The table

Action	Owner	Admin	Member	Viewer
See every project in the organization	yes	yes	yes	yes
Open a project and read its chat	yes	yes	yes	yes
Browse and read the source	yes	yes	yes	yes
Download the whole source as a zip	yes	yes	yes	yes
Read version history	yes	yes	yes	yes
Run the security check	yes	yes	yes	yes
See the publish status and live URL	yes	yes	yes	yes
Watch a build happening	yes	yes	yes	yes
Create a project	yes	yes	yes	no
Send a message / start a build	yes	yes	yes	no
Cancel a running build	yes	yes	yes	no
Use "Get me unstuck"	yes	yes	yes	no
Apply the security check's fixes	yes	yes	yes	no
Restore a version	yes	yes	yes	no
Rename a project	yes	yes	yes	no
Change a project's design	yes	yes	yes	no
Star a project	yes	yes	yes	no
Archive a project	yes	yes	yes	no
Delete a project	yes	yes	yes	no
Publish, republish, rename the address, take offline	yes	yes	yes	no
Create a new organization	yes	yes	yes	yes
Invite, remove or re-role a member	—	—	—	—
Rename or delete an organization	—	—	—	—

The dashes in the last two rows are not omissions. No role can do those things in Bookbag, because member and organization management happens at your Bookbag account, not here. See Organizations.

What "read everything" really means for a viewer

Be deliberate about this before you add someone as a viewer. A viewer can:

• open every project in the organization, including ones they had nothing to do with,
• read the entire chat history of each one, prompts and all,
• read every file of the generated source,
• download the complete source of any project as a zip,
• read every version ever recorded, including the contents of deleted files,
• see the findings of the security check.

A viewer is read-only, not restricted-visibility. There is no per-project sharing, no private project, and no way to hide one project from someone who is in the organization.

If a project must not be seen by someone, they must not be in that organization. Put the project in a different organization instead.

What a viewer sees when they try

The interface does not hide the controls. A viewer sees the prompt composer, the Rename item, the Delete item, the Publish button — all of them enabled. The refusal arrives when they click.

Two different messages, because two different paths:

Creating a project returns:

You can only view <organization> — ask an admin there for member access.

Everything else returns:

You can view this project but not change it.

There is one deliberate visual signal: the dashboard's subtitle reads "Viewing <organization> — you can open projects here but not change them" instead of "Building in <organization>".

Other denial messages

Message	When
Sign in first.	Your session ended.
A valid project id is required.	A malformed request. Reload.
That project does not exist.	The project was deleted, or the link is wrong.
You do not have access to that project.	You are in no role in that project's organization. Also what you briefly see if the account service is unreachable, since Bookbag will not guess.
That run does not exist.	The build run in the link is gone.

Credits are per person, not per organization

Your credit balance is yours, and it travels with you across every organization you belong to. Building in a colleague's organization spends your credits, not theirs. Your monthly allowance is yours. There is no shared organization balance.

The same is true of your own AI provider key: it is attached to you, so a build you start runs on your key wherever you start it. See Credits.

Platform administrator

A fifth role, and not an organization role at all. A platform administrator runs the installation: the AI providers and models everyone builds on, the builder's skills, the design library, everyone's credits, and where sandboxes run.

You become one in one of two ways: your email address is on the installation's administrator list, or an administrator at your Bookbag account has marked you as an admin for this product.

If you are one, a Platform admin item appears in the sidebar and in your account menu. If you are not, it appears nowhere, and typing /admin bounces you back to the dashboard with a 403 from the server.

One detail worth knowing if you administer an installation: an administrator designated at your Bookbag account gets the whole /admin area, but cross-organization access to projects is granted only to addresses on the installation's own administrator list. The two checks are not identical.

See Administration.

Next

• Your account.