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

# Organizations and Workspaces

> Understand where resources and access rules are stored.

An **Organization** is the top-level account boundary. It contains people, Workspaces, roles, and assignments.

A **Workspace** is the operating boundary for a team. Agents, Channels, MCP providers, Gateways, credentials, Traces, and Analytics belong to a Workspace.

<img src="https://mintcdn.com/groundforgeai/V4bCNZADLwZmOUhb/images/concepts/organization-workspaces.svg?fit=max&auto=format&n=V4bCNZADLwZmOUhb&q=85&s=02772e8e0f1bd9d7b1b56d9b5a342f2d" alt="Acme Organization with separate Support and Finance Workspaces" width="1000" height="680" data-path="images/concepts/organization-workspaces.svg" />

Always check the active Organization and Workspace before creating a resource or reading a Trace. The web application and CLI send that context with each request.

## Example

The Support team can operate a WhatsApp weather Agent without seeing the Finance team’s email Agent, credentials, or request history. An Organization administrator can still manage access across both Workspaces.

See [Organizations](/administration/organizations), [Workspaces](/administration/workspaces), and [CLI Context](/cli/context).


## Related topics

- [Organizations](/administration/organizations.md)
- [Workspaces](/administration/workspaces.md)
- [Resource Model](/concepts/resource-model.md)
- [Context](/cli/context.md)