diff --git a/docs.json b/docs.json index 8607adfd..f01e4fd7 100644 --- a/docs.json +++ b/docs.json @@ -287,6 +287,17 @@ "accounts-billing/add-tax-id" ] }, + { + "group": "Organizations (Beta)", + "pages": [ + "organizations/orgs-overview", + "organizations/orgs-access", + "organizations/org-roles", + "organizations/orgs-groups", + "organizations/orgs-resource-tagging", + "organizations/orgs-billing" + ] + }, { "group": "Integrations", "pages": [ diff --git a/organizations/org-roles.mdx b/organizations/org-roles.mdx new file mode 100644 index 00000000..7dbdbc75 --- /dev/null +++ b/organizations/org-roles.mdx @@ -0,0 +1,48 @@ +--- +title: "Roles" +sidebarTitle: "Roles" +description: "Control what organization members can do with four built-in roles. Learn which actions each role can perform." +--- + +Every member of an organization is assigned one of four built-in roles: admin, billing, dev, or basic. There is no owner role; admin is the highest level. Only org admins can assign or change member roles. + +## Role overview + +| Action | Admin | Dev | Billing | Basic | +|---|---|---|---|---| +| Manage members, groups, and org settings | ✓ | — | — | — | +| View member roster | ✓ | ✓ | ✓ | ✓ | +| Create and manage compute resources | ✓ | ✓ | — | — | +| View and use existing compute resources | ✓ | ✓ | — | ✓ | +| Manage billing and cost centers | ✓ | — | ✓ | — | +| View all members' usage | ✓ | — | ✓ | — | +| View own usage | ✓ | ✓ | ✓ | ✓ | + +## Role descriptions + +**Admin.** Full organization management. Admins can invite and remove members, manage groups and roles, update org settings, and create, update, or delete any org resource. Assign this role to team leads who need full control. + +**Dev.** Full compute access with no billing or member management. Devs can deploy Pods, create Serverless endpoints, manage network volumes, Instant Clusters, and templates. They cannot view billing, manage cost centers, or manage members or groups. Assign this role to engineers and researchers who build and run workloads. + +**Billing.** Financial management only, with no access to compute resources. The billing role can view all members' usage in Billing Explorer and manage cost centers. They cannot view, create, or interact with any compute resource. Assign this role to finance staff who need billing visibility without operational access. + +**Basic.** Read and use access to existing resources. Basic members can view and connect to existing Pods, endpoints, volumes, and clusters, but cannot create new resources. Assign this role to members who need access to existing workloads without deployment permissions. + +## Assign a role + +Only admins can assign or change member roles. Role changes take effect immediately. + + + + Go to **User management** in the console and select the **Users** tab. + + + Locate the member whose role you want to change. + + + Click the role dropdown next to their name and select the new role. + + + Confirm the change. The new role takes effect immediately. + + diff --git a/organizations/orgs-access.mdx b/organizations/orgs-access.mdx new file mode 100644 index 00000000..f091d134 --- /dev/null +++ b/organizations/orgs-access.mdx @@ -0,0 +1,55 @@ +--- +title: "Access" +sidebarTitle: "Access" +description: "Control who joins your organization with email invitations. Learn how to invite, accept, and remove members." +--- + +Runpod provisions organization accounts. Once your org is provisioned, org admins invite members by sending invitations to their exact email addresses. Only admins can invite and remove members. + +## Invite a member + + + + Go to **User management** in the console and select the **Users** tab. + + + Click **Invite Member**, enter the member's exact email address, select their role, and send. + + + +The invited user receives an email with a link to accept. They must have a verified Runpod account to accept the invitation. + +Invitations expire after 14 days. Each organization can have up to 150 pending invitations at a time. Admins can cancel a pending invitation from the **Users** tab. + +## Accept an invitation + +To accept an org invitation, the invitee must not be a member of any Runpod team. If they belong to a team, they must leave or delete it before the invitation can be accepted. + + + + Click the link in the invitation email. + + + Sign in to Runpod with the account associated with the invited email address. + + + Accept the invitation in the console. + + + + +Accepting an org invitation does not move personal resources into the organization. Existing Pods, endpoints, network volumes, and other personal resources remain on the member's personal account unless migrated by Runpod staff separately. + + +## Remove a member + + + + Go to **User management** in the console and select the **Users** tab. + + + Find the member and click **Remove**. The member is removed from the organization immediately. + + + +When a member is removed, their org S3 credentials are revoked immediately. Their Pods, endpoints, and other org resources remain in the organization. diff --git a/organizations/orgs-billing.mdx b/organizations/orgs-billing.mdx new file mode 100644 index 00000000..a9254c7a --- /dev/null +++ b/organizations/orgs-billing.mdx @@ -0,0 +1,23 @@ +--- +title: "Billing" +sidebarTitle: "Billing" +description: "Understand how organization billing works, including post-paid invoicing, Billing Explorer access, and cost centers for spend attribution." +--- + +Organizations are billed on a post-paid invoice model. Usage from all members accrues throughout the month and is invoiced by Runpod's finance team. There is no credit balance, credit top-up, or payment method to manage in the console. + +## Billing Explorer + +Billing Explorer shows resource usage broken down by member, resource type, and time period. All members with access can open it from **Billing** in the console left nav. + +Admin and billing roles see usage for all org members. Dev members see their own usage only. + +## Cost centers + +Cost centers let you attribute spend across projects, teams, or departments by tagging resources with a cost center label. Admin and billing roles can create, update, and delete cost centers. + +To create a cost center, go to **Cost centers** in the console and click **Create cost center**. + +## Invoices and payment + +Invoices are issued by Runpod's finance team at the end of each billing period. For invoice questions, payment terms, or billing disputes, contact your Runpod account team directly. diff --git a/organizations/orgs-groups.mdx b/organizations/orgs-groups.mdx new file mode 100644 index 00000000..107a6e0a --- /dev/null +++ b/organizations/orgs-groups.mdx @@ -0,0 +1,72 @@ +--- +title: "Groups" +sidebarTitle: "Groups" +description: "Organize organization members into groups to control resource visibility and structure teams within your organization." +--- + +Groups let you organize members by team, project, or function. Only org admins can create groups and manage membership. + +## How groups work + +Groups are leaderless and additive. There is no group owner or group-level admin. A member can belong to zero or many groups at the same time, and joining one group has no effect on membership in any other. + +## Resource visibility + +Groups control which resources members can see in the console. By default, a member can only see resources they created themselves. When a resource is assigned to a group, all members of that group can see it, regardless of who created it. + +Admins can see all resources across the organization, including resources that belong to no group and resources in groups they are not a member of. + +## Create a group + + + + Go to **User management** in the console and select the **Groups** tab. + + + Click **Create a new group**, enter a name, and confirm. + + + +## Add a member to a group + + + + Go to **User management → Groups** and find the group. + + + Click **Add a user to this group**, enter the member's name or email, and select them. + + + +## Remove a member from a group + + + + Go to **User management → Groups** and find the group. + + + Click **Remove from group** next to the member's name. This removes them from the group only — they remain in the organization. + + + +## Rename a group + + + + Go to **User management → Groups** and find the group. + + + Click **Rename**, enter the new name, and confirm. + + + +## Delete a group + + + + Go to **User management → Groups** and find the group. + + + Click **Delete this group** and confirm. Members in the group are not affected and remain in the organization. + + diff --git a/organizations/orgs-overview.mdx b/organizations/orgs-overview.mdx new file mode 100644 index 00000000..6186b3a2 --- /dev/null +++ b/organizations/orgs-overview.mdx @@ -0,0 +1,39 @@ +--- +title: "Organizations" +sidebarTitle: "Overview" +description: "Manage enterprise GPU workloads with centralized resource ownership, post-paid billing, and role-based access control." +--- + +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](/organizations/migrate-from-teams). + + +## How Organizations differ from Teams + +| | Teams | Organizations | +|---|---|---| +| **Resource ownership** | Resources owned by the team owner's user account | Resources owned by the organization, surviving if any member leaves | +| **Billing** | Prepaid credit balance | Post-paid invoice only. No credit balance or payment method management in the console. | +| **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 | Mutually exclusive with Teams, permanently | + + +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](/organizations/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](/organizations/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](/organizations/billing). + + diff --git a/organizations/orgs-resource-tagging.mdx b/organizations/orgs-resource-tagging.mdx new file mode 100644 index 00000000..102e9ef8 --- /dev/null +++ b/organizations/orgs-resource-tagging.mdx @@ -0,0 +1,36 @@ +--- +title: "Resource tagging" +sidebarTitle: "Resource tagging" +description: "Attach key-value tags to organization resources to track spend, filter usage, and attribute costs across teams, projects, and cost centers." +--- + +Resource tagging is available to organization accounts only. Tags are key-value pairs you attach to org resources to track spend, filter usage, and attribute costs across teams or projects. Tagging is supported on Pods, Serverless endpoints, network volumes, and Instant Clusters. + +## Tag format + +- Tag keys must be non-empty. Tag values may be left blank. +- Each resource supports a maximum of 25 tags. +- The combination of key and value must be unique on a resource. +- Keys using the `runpod:` prefix are reserved for system use and cannot be created. +- All org members can view all tags regardless of who created them. +- Admin and dev roles can create, edit, and delete tags. Basic members can apply existing tags to resources. Billing members can only view tags. + +## System tags + +Runpod automatically manages one reserved tag: `runpod:cost-center`. This tag is applied by the system when you assign a resource to a cost center. You cannot create or modify tags that use the `runpod:` namespace prefix. + +## Add a tag + +You can add tags when deploying a new resource or after deployment by editing an existing resource. + +**During deployment:** In the deploy form, expand the **Tags** section. Click **Add Tag**, enter a key and value, and continue with deployment. + +**On an existing resource:** Navigate to the resource in the console and open its details. Click **Tags**, then **Add Tag**. Enter a key and value and click **Save**. + +## Remove a tag + +Navigate to the resource in the console and open its details. Click **Tags** and click the delete icon next to the tag you want to remove. + +## Filter by tag + +Use tags to filter resources in the console or query usage by tag in Billing Explorer. This helps attribute spend to specific teams, projects, or cost centers.