Spaces
A Space is the container that owns your work. Datasets, connectors, model designs, training runs, inference servers and audit records all belong to exactly one Space, and nothing crosses the boundary between two Spaces.
If you are looking for a single mental model for the platform, this is it: you are always working inside a Space, and what you can see and do is decided by the seats you hold in that Space.
Spaces in the URL
Every in-product screen carries its Space in the path:
/spaces/<spaceId>/neodata/<area>
For example:
| Screen | Path |
|---|---|
| Home | /spaces/<spaceId>/neodata/home/dashboard |
| Datasets | /spaces/<spaceId>/neodata/datasets |
| Pre-training runs | /spaces/<spaceId>/neodata/pre-trainings/runs |
| Space settings | /spaces/<spaceId>/neodata/settings/general |
Signing in without a Space in the path lands you on the Space picker at /spaces,
which lists the Spaces you are a member of. Picking one takes you to its Home; the
application remembers the last Space you were in and returns you there on your next visit.
The same rule applies to the API: space-owned resources are addressed as
/v1/spaces/{spaceId}/....
Space request header is deprecatedOlder integrations passed the Space as a Space: request header instead of a path
segment. That header still works for resources that have not finished migrating, but it is
going away. New integrations must build the /v1/spaces/{spaceId}/... path explicitly.
See Permissions for how the Space is resolved during
authorization.
What a Space isolates
- Resources — a dataset created in Space A is invisible from Space B. There is no "move to another Space" operation; you re-create the resource where you need it.
- Permissions — your access is granted per Space through seats. Holding an administrator seat in one Space grants you nothing in another.
- Activity — the Activity Log inside a Space records only that Space's events. Organization administrators get a cross-Space view under Settings → Activity.
- Compute — clusters are provisioned at the organization level and assigned to Spaces. A Space sees only the clusters assigned to it; the full inventory lives under Settings → Clusters.
Space settings
Two screens, both in the sidebar under Space:
General — the Space's name and description, plus its provenance (who created it and when, and when it was last updated). Every member can open this screen; editing is gated by permission.
Members — who belongs to this Space. Invite by email, or remove a member. Membership here is what makes the Space appear in someone's Space picker.
Spaces, seats and the organization
A Space sits inside an organization. Above the Space, and reachable from the gear icon
next to your avatar, is the settings hub at /settings:
- Spaces — every Space you belong to. Administrators see every Space in the organization.
- Members — the organization-wide user list.
- Seats — the grant that connects a user to a Space with a set of permissions. One seat can cover several Spaces, and a user can hold several seats in the same Space; access is granted if any of their seats allows the action.
Read Permissions for the full resolution model.
Next steps
- Home — what you land on inside a Space.
- Permissions — seats, roles and how access is decided.