Access levels

Summary

What a person can do in a product. The four levels are the whole list.

Canonical values

Level	Can do	Uses a seat
Owner	everything, including billing and removing people	yes
Can merge	everything Can edit does, plus merge a branch to main and add a tag	yes
Can edit	capture, edit in their draft, save it as a branch, run Verify, invite	yes
Can view	open main and any branch, preview, read Analysis, and use everything in View	no

Every level has View. The bottom toolbar has one switch, View · Edit, and View is the default. View is looking and taking: switching states and viewports, reading an element's values, copying its code, trying an icon in a colour, and Preview. The CLI and MCP read what View shows. Edit is for Owner, Can merge and Can edit; Can view sees it locked. See 2026-10-18-editor-redesign.

Roles are not access levels. A role (Open, User, CA, Admin) is a kind of user of the captured product. An access level is what a person can do in Babul.

Nobody edits main directly. Every change goes to a draft, is saved as a branch, and is merged.

One owner per client. Billing is per client, so the owner is the client's, not a product's.

Who can open a product is set per product, not by access level: Everyone in the company (the default) or Chosen people. The owner can open every product. See 2026-10-13-product-access.

Related

• branch-verify-merge · settings
• plans · 2026-10-14-git-model

Sources

• .context/designs/web/northwind/settings/members.html
• The owner's instructions in the session of 2026-10-14.