> For the complete documentation index, see [llms.txt](https://docs.pipekit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pipekit.io/concepts/organization.md).

# Organization

An Organization is Pipekit's top-level tenant. It owns your [Clusters](/concepts/cluster.md), [Pipes](/concepts/pipe.md), members, alert providers, secrets environments, and identity provider integration.

Organizations are isolated from each other. Members of one Organization cannot see another Organization's Pipes or Runs; access control, SSO mappings, and audit boundaries all stop at the Organization boundary.

When you first sign up to Pipekit Cloud, you'll be prompted to create an Organization. Self-hosted deployments start with a single Organization that you bootstrap as part of the install.

Within an Organization, [Access Control](/concepts/access-control.md) further scopes who can see and act on Pipes, Runs, and Clusters via workspaces, roles, and IdP group bindings.

For task-oriented documentation, see [Organizations & Access](/organizations-and-access.md).