Description
Workspace Onboarding and Platform Operations combine buyer-estate setup with the protected operator plane used to observe and maintain the hosted Dots service. dots onboarding, dots workspaces, dots workspace-templates, and dots spaces create and shape buyer environments. dots platform uses separate operator authentication for tenant, metric, job, operator, and operational-seed commands.
The workflow is designed for operators and coding agents. It uses the same authenticated, company-scoped service contracts as the rest of Dots, so terminal or protocol convenience never creates a second source of truth. Inputs are validated before or at the route boundary, and outputs preserve identifiers and structured details needed for a reliable next step.
Selling Points
- Turns workspace onboarding into a repeatable, idempotent terminal process.
- Supports per-member seeded estate templates rather than empty generic workspaces.
- Lets administrators restyle and order Spaces while preserving locked-name rules.
- Separates staff operator authority from ordinary company credentials.
- Provides hosted overview, metrics, tenant, job, and operator controls in one protected plane.
User Story
An administrator invites a buyer, creates the workspace, provisions the approved member template, and adjusts Space presentation. A Dots operator separately signs into the platform plane to confirm tenant health and inspect operational jobs without borrowing buyer credentials. The result is a concrete, inspectable outcome that another person or automation can continue from without reconstructing hidden state.
Extension Surface
The family is automatable: packages/cli/src/commands/onboarding.ts, packages/cli/src/commands/workspaces.ts, and packages/cli/src/commands/platform.ts expose fixed operational routes. Template data is configurable, but command registration is closed. The rating reflects the most-open supported seam that is true for this capability, not a transitive implementation detail. The cited path is the operational proof: consumers can use the documented seam, while unsupported changes still require a core release.
Capabilities & Limits
- Capability: Invitations, workspace creation, template provisioning, and Space management.
- Capability: Separate platform operator login and identity lifecycle.
- Capability: Operational seed, overview, metrics, tenant, job, and operator administration.
- Limit: Platform commands are intentionally staff-only and cannot be reached with ordinary workspace authority; external provisioning such as DNS remains separate.
The limit is intentional product truth rather than missing documentation. Calls also remain subject to authentication, tenant selection, schema validation, and the permissions enforced by the authoritative service.
Implementation Map
packages/cli/src/commands/onboarding.tspackages/cli/src/commands/workspaces.tspackages/cli/src/commands/platform.ts