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.
How Organizations differ from Teams
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. 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. 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. 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. Resource tagging — Tags are key-value pairs attached to resources for cost attribution and filtering. See Resource tagging.Get started
Roles
Understand what each role can do
Groups
Organize members within your Organization
Billing
How post-paid invoicing works
Access and SSO
Configure SSO, invitations, and IP allowlists
Resource tagging
Tag resources for cost attribution
Migrate from Teams
Move your Team account to an Organization