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

> Understand and administer the top-level GroundForge boundary.

An Organization is the top-level administrative boundary in GroundForge. It contains Workspaces and defines where membership, high-level administration, and shared access are managed.

Use a separate Organization when resources and administrators need to be kept fully apart from one another. Day-to-day Agent and Channel work happens inside a Workspace, not directly at Organization scope, so most people will spend very little time here once it's set up.

## Organization settings

An Organization record includes an identifier, display name, status, description, and metadata. Organization administrators can create Workspaces and manage access that applies across the whole Organization.

## Scope matters

Always confirm the selected Organization before creating a Workspace, assigning an Organization-wide role, or issuing a credential. The active Organization is part of the request scope used by both the web application and the CLI, so getting it right up front avoids resources ending up in the wrong place.

## CLI examples

```bash theme={null}
gforge organizations list
gforge organizations describe <organization-id> -o yaml
gforge organizations create <organization-id> --dry-run -o yaml
```

Use dry run to preview a create or update payload before you change any administration resource.

Next: [Workspaces](/administration/workspaces).

Related: [Organizations and Workspaces](/concepts/scope).


## Related topics

- [Organizations and Workspaces](/concepts/scope.md)
- [Onboarding Create Organization](/api-reference/endpoints/onboarding-create-organization.md)
- [Resource Model](/concepts/resource-model.md)
- [LangChain Agent Example](/examples/langchain-agent.md)