Browse documentation

Spaces

The mental model behind Spaces: a shareable container for a use case.

A workspace fills up quickly. As a team works, it accumulates data objects, canvases, tasks, files, workflows, and agents across many unrelated jobs. A Space is how you carve one use case out of that pile and give it a home.

What a Space is

A Space is a use-case container. It groups the pieces that belong to a single job to be done, such as "Counterparty monitoring" or "Quarterly reporting," so the people working on that job see what's relevant and skip everything else.

A Space brings together the data objects, canvases, and agents for a use case, and the related tasks, files, and workflows sit alongside them. It's the difference between handing someone a whole warehouse and handing them the one shelf they need.

What a Space is not

A Space is not a folder, and it doesn't move or copy anything. The underlying objects still live in the workspace; a Space is a curated lens onto them. That's why the same data object can appear in several Spaces at once, because a single dataset often matters to more than one team.

Why Spaces matter

Spaces turn a growing workspace into something a team can actually navigate:

  • Focus: everything for one use case is in one place, and nothing else is in the way.
  • Consistency: everyone working the use case sees the same curated set.
  • Onboarding: a new teammate gets a ready-made starting point instead of a blank workspace.
  • Context for the Agent: working inside a Space gives the Agent a clear picture of what the use case involves.

How it relates to the rest

A Space sits above the individual objects. It doesn't replace data objects, canvases, or agents; it arranges them for a purpose. Think of data as the raw material and a Space as the workbench where one job's material is laid out.

The Spaces section covers how to create a Space and add items to it.