Spaces

A space divides an organization's work and decides who can reach it. Models live in spaces, and access is granted on the space, not model by model.

That is the point of spaces. Giving someone a role on a space gives them everything in it, now and later, instead of a share for every model you create. Plan your spaces around who needs to work together: a team, a project, a client.

The three kinds

Every space is one of three kinds, and the kind decides where it can sit.

• Restricted is the ordinary top-level space: only the people you add can see it and open it.
• Sealed is for confidential work. Nothing inside can leave it: no exporting, no sharing outside the space, no importing its tables elsewhere, and no access for AI assistants. See Sealed spaces.
• Open spaces nest. An Open space inherits everything from the space above it: who can open it, at what role, and whether it sits behind a wall.

The rule in one line: Open nests; Restricted and Sealed are top-level. An Open space with nothing above it would have nothing to inherit, which is what a Restricted space is.

Create a space

Any member of an organization can create a top-level space, and becomes its first manager.

1. In the sidebar, hover over Spaces and choose New space.
2. Name the space and pick its kind under Kind of space: Restricted or Sealed.
3. Confirm.

To create an Open space inside an existing one, hover over that space in the sidebar and choose its New space. A manager of the parent space can do this.

Roles in a space

• Managers own every model in the space. Creating a model does not make you its sole owner; the space's managers own it with you.
• Roles flow down into Open spaces. A collaborator on a space is a collaborator on every Open space beneath it.
• A viewer is implied. Collaborators and managers can also view, so you never grant both.
• A guest can never be a manager. In a personal organization you can grant collaborator or viewer to people outside it; they show as Guest.

Manage access

1. Hover over the space in the sidebar and choose Space settings, then Access.
2. Enter an email address and pick a role.
3. Confirm.

To remove someone, open their row and choose Revoke Access. A space always needs a manager, so the app asks you to Add another manager before you revoke your access if you are the last one.

The General tab shows the space's name and color, its kind, and an Access inheritance line: Top level: nothing is inherited, or where an Open space's access comes from.

Organization owners and admins

An organization's owners and admins govern every space: they can rename it, delete it, and appoint managers. What they do not get is standing read access. As the app puts it, org admins govern this space but can't read it. Reading takes a grant, which shows in Access like any other.

That makes reading someone's space an act everyone can see, recorded in the governance log, rather than a silent privilege.

A space with no manager

If its last manager leaves or is removed, a space has nobody who can grant access to it or own its models. Its settings say This space has no manager, and the organization's Spaces settings flag it. An owner or admin fixes it with Assign manager.

Sealed spaces

Sealing puts a wall around a space. Seal space is offered in the space's settings while it is still empty, and the confirmation says exactly what changes:

Only the people you add to this space will see it, and nothing inherits in. Its data stays inside: it can't be exported, copied, imported elsewhere or shared one model at a time.

Inside a sealed space:

• Nothing inherits in. Access must be granted on the space itself.
• Nothing leaves. No exports, no copies, no importing its tables into models outside, no sharing a single model, and no reading by AI assistants.
• It is invisible to anyone without a grant.

Every Open space nested inside a sealed one sits behind the same wall. Walls do not nest: a sealed space is always top-level.

Unsealing

Unsealing is declassification, and it is not the manager's to do: only an organization owner or admin can choose Unseal space. A manager works inside the wall and can appoint more managers, so a manager's unseal would let the people inside decide the wall no longer applies.

Its data can be exported, copied and shared again. Sub-spaces sealed only because this one was are unsealed with it; any sealed on their own stay sealed. Nobody gains or loses access, and the change is recorded in the governance log.

Delete a space

Deleting a space takes everything under it: every Open space nested inside, and every model in any of them.

1. Open Space settings and choose Delete space.
2. Read the analysis of what will go, including the people whose only access is through this space, and the models outside it that import from it, which lose their source.
3. Type the space name to confirm, and choose Delete space.

The space and everything beneath it enter one 30-day window, on one clock, and every model inside goes to the Trash. Deleted spaces are hidden from everyday working surfaces, so nobody builds on something about to disappear.

During the window, a manager restores the whole space, models included, from the Trash, or an owner or admin cancels from the organization's Spaces settings. You restore the space where the deletion started, not a branch of it.

Move a model between spaces

A model can move to another space in the same organization: open its menu on the overview and choose Move to space. You must manage both spaces. A model cannot move into or out of a sealed space, because that would carry data through the wall. See Models.