A space is the unit above the project: one team that manages every project in it, and the group the project launcher is arranged by. Every project belongs to exactly one space, and every account gets one: a new account's first screen asks Personal (a space named after you) or Business (the company's name) and creates it — or Skip for now leaves it for later, and the project wizard creates one the first time it is needed. Accounts invited into an existing space — or into one of its projects — skip the question: a short Welcome step asks for their name, photo and language and continues to the project list. Inviting someone to a space sends them an invitation e-mail. Account → Spaces lists yours; the project wizard's first page picks one of them or creates another.
The space's cloud#
A space on the Business plan can connect its own Firebase project — every project created in it afterwards keeps its data there. Its cards sit on the space page under Advanced Cloud, collapsed until you open it; they and the checklist are described on the Space cloud page.
Space tier#
A space is Basic (tier 0), Enterprise (tier 1) or Partner (tier 2). Only a platform administrator sets it, on the space page. An Enterprise or Partner space shows its tier as a badge next to its name (on the page and in Account → Spaces), and its projects get the SDK setup in Settings › Advanced (other spaces see a note to contact the inmake team at inmake@insightbase.cz there). The space tier is separate from each project's plan.
Roles#
| Role | What it grants |
|---|---|
| Owner | Exactly one per space. Everything an admin may do, plus transferring ownership and deleting the space (only while it has no projects). Cannot be removed or leave — transfer first. |
| Admin | Manages the team (never the owner), renames the space, creates projects, and is a manager in every project of the space — including projects where they hold no team entry. |
| Member | Sees the space, its team and its project list. In a project, exactly what that project's own Team page grants; a project the member has no entry in shows as an inert card. |
Platform roles sit above these: master and administrator manage every space; a developer is a manager of the projects of every space they belong to. The project Team page lists the space's managers read-only under the project roster.
The Demo switch on a space member lets them open the space's projects on the Demo environment, in addition to any per-project grant.
Creating and assigning projects#
New project on a space's section of the launcher (or on its page) opens the wizard with that space preselected. A project created before spaces existed sits in the launcher's Unassigned section; a manager attaches it from the project menu — Assign to space….
Transferring a project#
A project can be moved to another space from Settings › Project details › Danger zone or from its menu on the launcher (Transfer to another space…). You need to be an owner or admin of both spaces. Pick the new space, read what changes, type the project id and confirm.
The project's team, plan and billing, credits, data and domains stay with it. Owners and admins of the old space lose access unless they are on the project's own team; owners and admins of the new space become its managers. The move applies to Production and Demo together. If Demo was left behind — the move failed there and the dialog was closed — opening Transfer again says so and offers Finish on Demo.
Two cases are refused: a project whose data lives in the old space's own cloud (moving that data is a migration the platform runs on request), and a project with a module owned by the old space installed (uninstall it first).
Transferring ownership#
Team → Transfer ownership on a member who has signed in at least once hands the space over; the previous owner stays on as an admin. The target's e-mail has to be retyped.
Deleting#
The owner can delete a space that has no projects left. Project data is never touched by space operations.