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

# Workspaces

> Use Workspaces to separate teams, applications, and environments.

A Workspace is the main operating boundary in GroundForge. Agents, Channels, MCP providers, Gateways, credentials, Traces, Observations, Drifts, and analytics belong to a Workspace.

Use separate Workspaces when teams, products, or environments need different resources and access.

## Example

A Support Workspace can contain the Support Agent, WhatsApp Channel, Ticket MCP, and support-team Traces. A Finance Workspace can contain a different Agent, email Channel, credentials, and access assignments.

## Active Workspace

The web application shows the Organization and Workspace selectors in the top bar. The CLI stores the same context locally.

Before creating a resource or reviewing a Trace, confirm that the correct Workspace is selected.

## CLI examples

```bash theme={null}
gforge workspaces list
gforge workspaces describe <workspace-id> -o yaml
gforge workspaces create support \
  --display-name "Support" \
  --dry-run \
  -o yaml
```

The Workspace ID is used by the API, SDK, and CLI. Keep it stable after creation.

Next: [Access](/administration/access). See also [Organizations and Workspaces](/concepts/scope) and [CLI context](/cli/context).


## Related topics

- [Organizations and Workspaces](/concepts/scope.md)
- [Get Workspace Runtime Analytics](/api-reference/endpoints/analytics/get-workspace-runtime-analytics.md)
- [Resource Model](/concepts/resource-model.md)
- [Platform Overview](/platform/overview.md)