Core concepts

Five nouns explain the whole platform:

Workspace
└── Project
    ├── Models          (the 3D files you upload)
    ├── Scenes          (camera, lighting, materials, annotations)
    └── Products        (configurator structure)
        └── Parts       (what the shopper picks: body, legs, cushion…)
            └── Variations   (the choices per part: walnut, oak, chrome…)

Workspace

The account container: team members, roles, subscription plan and workspace-level settings such as the embed domain allowlist. One organization typically uses one workspace; agencies use one per client.

Project

One sellable product experience — the unit you publish, share and embed. A project holds models, scene setups and (optionally) a configurator.

Model

A 3D file you upload (GLB/GLTF). The platform optimizes every upload automatically for web and AR delivery — compression, texture encoding and AR format derivatives happen without your involvement. See Preparing models.

Product, part, variation

The configurator structure on top of your models:

• A product is what the shopper configures (a project can hold several).
• A part is one configurable slot: body, legs, cushion.
• A variation is one choice for that part: walnut, oak, chrome. A variation can swap geometry, material, or both, and carries the SKU your store receives.

Relationships between parts — “these two finishes always match”, “this leg only exists for the wide body” — are expressed with link groups, visibility groups and rules. See the Configurator section.

Unpublished vs. published

A project is unpublished until you publish it, and only published projects are publicly reachable — share links, QR codes and embeds are all closed until then. Owners can preview an unpublished project with a signed preview token.

Publishing is a switch rather than a snapshot: once a project is live, share links, QR codes and embeds serve the work as you save it. Unpublish first if you need to rework something visible.