> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentsfleet.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace overview

> Understand what a workspace owns and separates.

# Workspace overview

## 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 and its members control access.

A fleet belongs to exactly one workspace. Secrets and connectors do not cross workspace boundaries.

The service creates a default workspace during account setup. The client selects the first available workspace after login.

## 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.

## Related pages

* [Manage workspaces](/workspaces/managing)
* [Secrets](/fleets/secrets)