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 independent of any individual member, including compute, storage, secrets, and templates.
Organizations are currently in beta. Runpod provisions organization accounts and enables them for your account. If you’re an existing Team account customer, see Migrate from Teams. How Organizations differ from Teams
Organizations and Teams are mutually exclusive. Accepting an organization invitation permanently removes you from any Team you belong to. Your personal resources fold into the organization and cannot be returned to personal ownership.
Key concepts
Ownership. The organization owns all resources, not the member who created them. If a member is removed or suspended, their Pods, endpoints, and volumes continue running under the organization.
Membership. A user can belong to at most one organization. Joining an organization is permanent and mutually exclusive with Team membership. There is no path back to a Team account once you join.
Roles. Every member is assigned one of four built-in roles: admin, billing, dev, or basic. There is no owner role; admin is the highest level. Roles control what a member can create, manage, or view across compute, billing, and org settings. See Roles for the full permissions matrix.
Groups. Groups are the social unit within an organization. They are leaderless and additive: a member can belong to zero or many groups simultaneously. Only org admins can manage group membership. See Groups.
Billing. Organizations are billed on a post-paid invoice model. Usage accrues throughout the month and is invoiced by Runpod’s finance team. There is no credit balance, credit top-up, credit code redemption, or autopay. All members can view their own usage in Billing Explorer; org admins can view any member’s usage. See Billing. 
