Account, Spaces, and roles
Personal accounts vs shared Spaces, what each role can do, and how join codes and access requests work.
Personal vs Space
Your account alone covers most flying: orders, firmware, the Hangar, a personal Forge workspace. A Space is a shared organization on top — common fleet, shared Forge projects, and team billing.
Roles
- Owner — everything, including billing and deleting the Space.
- Manager — members, seats, fleet operations.
- Operator — day-to-day: fly, edit Forge parts, manage aircraft.
- Viewer — read-only.
Roles are per-Space; your personal account is unaffected by them.
Joining a Space
Two paths:
- Join code — an admin shares a code (they're role-scoped and can expire or have limited uses). Enter it under Account → Spaces.
- Access request — request to join, or request a new Space; an admin approves or denies it. You'll see the request status on the same page.
API keys
Scoped API keys for fleet integrations exist, but they are not self-service yet: SpaltX staff issue and revoke them for a Space on request, and there is no key management screen under Account → Spaces. Open a ticket if you need one, and say which scopes the integration requires.
A key's plaintext is shown once at issue and never again — store it in a secrets manager on receipt, and ask us to revoke any key you can't account for. The public API those keys are meant for is still being built, so a key is not usable for live traffic today.
Common questions
- Leaving a Space never deletes your personal data or entitlements.
- One account can belong to several Spaces. There is no global Space switcher yet — the Forge billing page is the one place that lets you switch between workspaces.
Still need help?
Open a ticket and a human picks it up. Include your order number and, for firmware issues, the board target — it saves a round trip.