Core concepts

SpaceSync has a small structural vocabulary. Getting these terms straight makes everything else — permissions, billing, sharing, versioning — follow naturally, because each of them attaches to exactly one level of this hierarchy.

Organisation           <org>.spacesync.app
├── Teamspace
│   └── Project
└── Project            (organisation root)

Personal               spacesync.app — and under "Personal" on any organisation host
└── Project
    ├── Iteration
    │   ├── SpaceDesign  (drawing)
    │   ├── SpaceModule  (model)
    │   └── SpaceSheets  (canvas)
    ├── SpaceStory       (narrative + phases)
    └── SpaceShow        (presentation)

Organisation

The top-level container for a team, a practice or a company. An organisation has its own address — <org>.spacesync.app — and owns its projects, its teamspaces, its members and their roles, its plan and seats, its audit log and its sign-in settings. Members hold one of four roles: Owner, Admin, Member or Guest.

Organisations are set up by SpaceSync rather than self-serve. You can belong to several and switch between them from the sidebar. See Organisations.

Teamspace

A group inside an organisation — a studio, a sector, a client team — with its own members and its own projects. A project that lives in a teamspace is editable by everyone in it. Teamspaces are created and managed by the organisation's admins; any member can be added to one.

Personal projects

Projects that belong to you rather than to an organisation. They are private — only the people you invite can see them — and they never appear in an organisation's admin views, audit log or usage. They live on spacesync.app, and when you are inside an organisation they are still there in the sidebar under Personal. If you leave an organisation, your personal projects go with you.

Project

One piece of work: a building, a fit-out, a masterplan. A project owns its brief, its site context, its AIRA programme, its collaborators and its sharing settings. Most permissions you will actually think about are set here.

Projects can be favourited and archived. Archived projects become read-only and move out of the main list — they are not deleted. See Organising projects. A project can also be moved between Personal, an organisation and a teamspace — see Organisation projects.

Iteration

A parallel attempt at the same project. Iterations are the answer to *"what if we pushed the core to the north instead?"* — you branch one, take it somewhere, and compare, without endangering the version you already like.

Design

The drawing or model itself — the document a module opens and edits. A design is what real-time collaboration synchronises, what autosave writes, and what a version snapshots.

Version

A named snapshot you can return to. Versions are append-only: restoring an old version does not delete the states after it, it adds the restored state as a new entry at the top of the history. Nothing you have saved is ever removed by a restore.

Versions and history covers snapshots, restores and what autosave does between them.

How the levels differ