Collaborators and protecting main
Give collaborators Full access, Branches or Isolated access, protect main so every change arrives as a reviewed merge, and see who can merge where.
Branches let you decide how each person changes your project: straight on main, only through merges you review, or on isolated branches that never see your real data.
Access levels
Open Collaborators with the + next to the avatars in the top-right of the project (see Sharing your projects). Each person's level is a pill beside their name; click it to change it. When you invite someone, pick their level before you send the invite. Only the owner manages collaborators.
| Level | What they can do |
|---|---|
| Full access | Edits main directly, and sees its data, keys and settings. Makes branches and merges them. New invites start here |
| Branches | Sees main and its data. On a team project, team builders at this level change main only through branches that are merged. On a personal project, a collaborator at this level views the project but doesn't make branches |
| Isolated | Never sees main, its data or its real keys. Works in their own branches, each an isolated branch with the code, an empty database and test keys. Can't publish them or connect them to anything outside |
An Isolated collaborator who opens the project's address sees their own branches and New branch, never main. Moving someone from Branches to Isolated closes the ordinary branches they made before, since those hold copied data. Access they already had open, such as a running preview, can last a few hours: remove and re-add the person when that matters.
What an Isolated collaborator can still see
Main's code and schema are what they are given to work on, so anything written into the code (a value in a file, a column default) is theirs to read, and comparing their branch with main shows main's current code and the names of its keys. What they merge runs on main: your review of the merge is the gate.
Protect main
In Collaborators, your own row is the protection switch for main: Main protected or Main not protected. With main protected, nobody edits main's code directly, you included: every change is made on a branch and arrives as a merge. Team projects have main protected by default.
- On a personal project only the owner merges into a protected main. On a team project everyone with Full access does.
- Your AI assistant can't merge into a protected main on its own: it shows you a merge card, and the merge starts when you click Merge.
- The owner's assistant can still change main's data with SQL, but not its tables: table changes go through a branch's migration script.
- Adding a Floot service on a protected main only attaches it; the starter code and tables for it arrive with a merge. A new connection to another of your apps is made on a branch and carried by the merge.
- Anyone who may make a branch can still ask their assistant to make one from a protected main.
Who can merge where
| Merge | Who |
|---|---|
| Into main, not protected | The owner and anyone with Full access |
| Into a protected main | The owner; on a team project, everyone with Full access |
| Into a branch | The project's owner and the branch's creator |
Marking a branch ready
When a collaborator's branch is ready to go into main, they mark it Ready. Ready branches are listed for review in Branch Reviews, where you can read the changes, comment, and merge. Ready is for merging into main; merging into your own branches needs no marking.