> ## Documentation Index
> Fetch the complete documentation index at: https://runpod-b18f5ded-lg-org-setup-team-mig.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Organizations

> Manage enterprise GPU workloads with centralized billing, access control, and resource ownership.

Organizations are Runpod's enterprise account model, designed for teams that need centralized resource ownership, billing, and access control. Unlike Teams, an Organization is a first-class entity that owns all resources — compute, storage, secrets, and templates — independent of any individual user.

<Note>
  Organizations are currently in internal alpha and are available to enterprise customers via Runpod sales. If you're an existing Team account customer, see [Migrate from Teams](/organizations/migrate-from-teams).
</Note>

## How Organizations differ from Teams

|                        | Teams                                            | Organizations                                                      |
| ---------------------- | ------------------------------------------------ | ------------------------------------------------------------------ |
| **Resource ownership** | Resources owned by the team owner's user account | Resources owned by the Organization — survive if any member leaves |
| **Billing**            | Prepaid credit balance                           | Post-paid invoice only                                             |
| **Membership**         | A user can own one team and belong to others     | A user belongs to at most one Organization                         |
| **Social unit**        | Team (has an owner)                              | Group (leaderless, additive)                                       |
| **Mutual exclusivity** | Compatible with personal accounts                | Joining an Org permanently removes Team access — irreversible      |

<Warning>
  Teams and Organizations are mutually exclusive — permanently. Once a user joins an Organization, there is no path back to Team membership. This is enforced at the data layer and cannot be undone.
</Warning>

## Key concepts

**Ownership** — All resources created inside an Organization are owned by the Organization, not the member who created them. If a member is suspended or removed, their resources keep running and remain accessible to other members.

**Membership** — A user may belong to at most one Organization. Joining an Organization folds your existing personal resources (Pods, templates, secrets, and more) into the Organization permanently. These resources cannot be reclaimed if you leave.

**Roles** — Four roles control what members can do: admin, billing, dev, and basic. There is no owner role — admin is the top level. See [Roles](/organizations/roles).

**Groups** — Groups are the intra-org social unit, replacing Teams within an Organization. Groups are leaderless and additive — a user can belong to zero or many groups. See [Groups](/organizations/groups).

**Billing** — Organizations use post-paid invoicing only. There is no credit balance, no credit top-up, and no payment method management in the console. See [Billing](/organizations/billing).

**Access** — Org admins control how users authenticate: SSO, ad-hoc email invitations, or both. Admins can restrict access by email domain or IP range. See [Access and SSO](/organizations/access).

**Resource tagging** — Tags are key-value pairs attached to resources for cost attribution and filtering. See [Resource tagging](/organizations/resource-tagging).

## Get started

<CardGroup cols={2}>
  <Card title="Roles" icon="user-shield" href="/organizations/roles">
    Understand what each role can do
  </Card>

  <Card title="Groups" icon="users" href="/organizations/groups">
    Organize members within your Organization
  </Card>

  <Card title="Billing" icon="receipt" href="/organizations/billing">
    How post-paid invoicing works
  </Card>

  <Card title="Access and SSO" icon="lock" href="/organizations/access">
    Configure SSO, invitations, and IP allowlists
  </Card>

  <Card title="Resource tagging" icon="tag" href="/organizations/resource-tagging">
    Tag resources for cost attribution
  </Card>

  <Card title="Migrate from Teams" icon="arrow-right-arrow-left" href="/organizations/migrate-from-teams">
    Move your Team account to an Organization
  </Card>
</CardGroup>