Layers
Everything in a scene sits in a layer. A layer decides who sees what it holds: the cells, the jobs that ran there, and the formulas behind its cells.
Every scene has three:
- Private. Yours. Every member has one, from their first day in the scene.
- Team. The team's working space, and the default in a team scene.
- Public. What the scene's share link and public page serve.
There is no separate permissions screen. The scene is laid out in its layers, so where a cell sits, and who it reaches in the app, is on screen.
Moving a cell changes who sees it
Drag a cell from Private to Team and your team has it. Move it on to Public and the scene's share link serves it. Moving it back takes it away again.
Nothing moves on its own. A cell never changes layer because of a migration, a bulk operation, or a new feature. It moves when someone moves it, and the confirmation says what changes: "Your team will see this."
Two moves are refused. A connected account never goes Public. And a cell can't go Private while cells made from it sit wider, like a spreadsheet under a Google account the team uses; the refusal names them.
A scene that has never moved anything into Public is the one exception to the Public rule: its share link shows everything except its members' Private layers, Team included. The first move into Public, or publishing the scene, narrows the link to Public alone, and it stays that way.
A cell's own link works in any layer
Moving a cell into Public shares it as part of the scene. A cell can also be shared on its own, by its link, without moving it. Copy a cell's link and the link turns on: anyone holding the URL can open that one cell, whether it sits in Team or in your Private layer. The app still shows it only to the people its layer allows, so a cell can be open to anyone with the link and private in the app at the same time. Its settings say when its link is on.
Two moves change the link too. Moving a cell into Public turns its link on, because the public page lists it; moving it into Private turns it off. Moves between other layers leave it as it was.
The URL is the key. It can't be guessed and isn't listed anywhere, but anyone you hand it to can open the cell, and so can anyone they hand it to. Turning the link off stops it on the next request, and turning it on again brings back the same URL. Resetting the link makes every URL handed out so far stop working, and the cell stays shared at a new one. A scene's settings can turn off every link in it at once, its public page included. To someone outside, a link that is off and a link that never existed look the same: nothing opens.
Turning a link on or off takes a member. An account never has a link. A view's link only reads, unless it is opened to filling in, which saves what its holder types into that view and nothing else. A model cell's link runs the model for whoever holds it, so it opens only once the cell has a daily budget and a budget per visitor.
A job runs in a layer
Jobs follow the same rule. A job you run in your Private layer is a rehearsal: full tools, full trace, and nobody else can open it. Try the risky prompt, take three attempts at the analysis, and when a run turns out well, move it to Team. It enters the team's history at that moment, outputs included.
A run only you are in turns private by itself the moment it opens one of your private cells, or you give it a secret only you may use. A run someone else has spoken in can't open those at all.
A scene has one job history, filtered by what you can see. Each row wears its layer. Teammates see Team and Public runs plus their own private ones; a share-link visitor sees Public runs only, as replayable traces.
One rule keeps rehearsal honest: a private job hides its conversation, never its effects. It reads with your eyes and writes wherever you can, and every change it makes shows in history under your name. To someone who can't open the run, it reads as a private run by you, with no title, no opening ask, and nothing of what it read.
A formula reads with its author's eyes
A cell's formula runs with the visibility of the person who saved it. Its output, and its text, are visible wherever the cell sits.
This is how data crosses layers on purpose. You author a cell in Team whose formula reads a model in your Private layer: the team sees the result, live, and can open the formula to read exactly what it does. What they cannot do is reach the source. Copying the formula into a cell of their own re-runs it with their eyes, and the private reference resolves as not found.
Mirko saves the formula
A teammate copies the text
Two consequences worth knowing:
- Publishing a formula publishes its text. The names of its private upstreams appear in it; their contents never do. The move gesture states this before you confirm.
- Authority ends with the author's. If the author loses access to an upstream, the cell keeps its last value and marks itself stale with the reason. It never silently computes with permissions that no longer exist.
Lower layers are substrate
The pattern scales past one cell. Keep the raw tables, the credentials, and the data model in a layer the team never has to scroll past, and publish projection cells into Team. The team works with clean numbers, the machinery stays out of their way, and the trace still records where every number came from.
A layer you name becomes a boundary when you name its readers
The three cover every scene. When some people should see part of a scene and not the rest, a client or a supplier, put that part in a child scene and invite them to it. A guest sees the one scene they are invited to and nothing else, and your team sees it like any other scene, its tile in the parent. Move a cell there from its menu.
Scenes made before 14 November 2026 can still have named layers, and they keep working: an admin can rename or remove one, and removing it never removes its cells, which fall back to Team.
Your Private layer is closed to admins too
Nobody else opens your Private layer: not a teammate, not an admin, not the workspace's owner.
A scene shared with another workspace works the same way at the workspace level. Each workspace gets a side of its own, and what you make there starts on your side, which only your workspace reads. Moving it to Team is how the other workspace sees it. Neither workspace's admins read the other's side.
What a layer does not do
If you know layers from a design tool, drop the compositing half: nothing here overrides anything. A layer holds one version of everything in it, and a cell has the same value whichever layer you reach it through. The stack is an architect's: data below, views above, and published results as the interface between them.
There are no per-cell exceptions inside a layer, and no secrecy between colleagues within one. If a teammate must not see it, it belongs in your Private layer, a layer their role can't read, or another scene. A layer has no history of its own either: the scene's one history covers all of its layers, so a layer can't be rolled back alone.
What's next
- Roles: what each person can do, and named roles.
- Identity: how a job borrows the access of whoever started it.
- Audit: who can read the history a layer filters.
Updated 2026-11-14