Skip to content

Organizations and workspaces ​

Organizations and workspaces are the standard DECA Cloud isolation model. Edge uses the same rows: an organization is the customer account, and a workspace is a folder under it that holds distributions and domains. Every organization has a default workspace.

The console and most /v1 paths use those names. Agents, tokens, and platform resources use the same rows as tenant_id and namespace_id.

Console and HTTPToken and platformMeaning
Organizationtenant (tenant_id)The DECA customer account
Workspacenamespace (namespace_id)An isolation boundary containing distributions and domains

How a request is bound ​

The access token always supplies tenant_id. Agents never pass or select a tenant. A missing tenant claim is rejected.

namespace_id can come from the token. When omitted, Edge uses that tenant's default namespace. A namespace from another tenant returns 403.

The web app shows organization and workspace in its URLs and labels.

HTTP aliases ​

The existing /v1 adapter still exposes two UI names:

  • GET /v1/organizations/{org_id}/workspaces
  • workspace_id as the optional workspace selector

The organization path does not let a token switch tenants: {org_id} must identify the token's own organization. Most calls can omit workspace_id and use the default workspace. The log stream is the exception and requires it explicitly.

These names describe the same organization and workspace rows; they are not separate resources.

See also ​