What it is
A workspace groups fleets, secrets, connectors, and access. Each workspace belongs to one tenant. A workspace is not tied to one source repository. Each fleet declares its own trigger source.Why it exists
Use separate workspaces when teams or environments need different fleets and secrets. Billing and provider settings remain at the tenant level.How it behaves
You create a workspace through the client or API. The tenant owns the workspace. The dashboard calls a tenant an account. An account has one owner, the person who signed up. The owner can invite members, who open and steer every workspace in the account. Only the owner stores secrets, connects integrations, and manages people. A fleet belongs to exactly one workspace. Secrets and connectors do not cross workspace boundaries. Account setup creates a default workspace. After login, the client keeps your previous workspace if it is still available; otherwise it selects the first available workspace.Limits
agentsfleet does not publish a workspace count limit. Service limits still apply to work inside each workspace.
The client has no remote workspace removal call. workspace delete only removes one workspace from local client state.