Skip to main content

Organizations and Workspaces

Use an organization to collaborate with a team and workspaces to organize its pipelines and edge nodes. Separate workspaces can represent environments, sites, or operational responsibilities while keeping the same Cloud interface.

Choose an organization​

Cloud supports personal and shared organizations. A personal organization is for your own work. Create a shared organization when you need to invite team members; shared-organization creation also provisions a default workspace.

Select the organization before creating resources. Its membership and roles determine who can operate its workspaces. Organization Settings provides member management and invitations for shared organizations. Personal organizations do not accept invitations.

See Access and API keys before assigning roles. A member is an operator with resource-management permissions, not a read-only viewer.

Create and select a workspace​

  1. Open the workspace list in the intended organization.
  2. Create a workspace and give it a name that explains its purpose.
  3. Choose the node-connectivity settings appropriate to the hosts it will manage.
  4. Wait for provisioning to complete before connecting nodes or deploying jobs.
  5. Open the workspace and use its Nodes, Pipelines, Keys, and Settings views.

Creation is subject to your organization's workspace quota. Contact [email protected] if you need additional capacity.

Each workspace provides an API endpoint and its own node-enrollment context. Keep workspace names and CLI profile names aligned so operators can tell a staging deployment from a production deployment before submitting a job.

Tune connection health​

Workspace settings expose node-health timing presets and custom values. These cover the heartbeat interval and the time thresholds used to recognize a node as connected, disconnected, or lost.

Choose settings that match the network between Cloud and your nodes. A reliable local connection and an intermittent wide-area connection may need different tolerances. Short thresholds detect interruptions sooner; longer thresholds allow more time for a transient connectivity problem to recover.

Review the confirmation when applying timing changes to a running workspace. These settings determine how Cloud classifies node connection health.

Plan environment dependencies​

Workspace separation gives teams a practical way to organize staging and production. Before deploying into a workspace, make sure its nodes can reach the intended sources, destinations, and secret providers. Use labels to identify host properties and select the right deployment targets.

For a repeatable release process, see CLI and delivery workflows. For connecting those hosts, see Fleet management.

LLM text version