From 752a81ef7f4d01203907da0f9e3592c3005635b9 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" Date: Wed, 14 Oct 2026 17:19:42 +0000 Subject: [PATCH 1/2] Rename Dev organization role to Developer --- accounts-billing/manage-accounts.mdx | 6 +++--- organizations/org-roles.mdx | 6 +++--- organizations/orgs-billing.mdx | 2 +- organizations/orgs-overview.mdx | 2 +- organizations/orgs-resource-tagging.mdx | 2 +- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/accounts-billing/manage-accounts.mdx b/accounts-billing/manage-accounts.mdx index 49b326997..7d197a331 100644 --- a/accounts-billing/manage-accounts.mdx +++ b/accounts-billing/manage-accounts.mdx @@ -56,7 +56,7 @@ Your account will gain access to the team's resources based on the role assigned Runpod provides four distinct roles to control access within team accounts. Each role includes specific permissions designed for different responsibilities. -| Permission | Basic | Billing | Dev | Admin | +| Permission | Basic | Billing | Developer | Admin | |------------|-------|---------|-----|-------| | Access team account | ✅ | ✅ | ✅ | ✅ | | Connect to existing Pods | ✅ | ❌ | ✅ | ✅ | @@ -85,9 +85,9 @@ The billing role focuses exclusively on financial management aspects of the acco Users with this role can access all billing information, manage payment methods, and view invoices. They cannot access computing resources, making this role ideal for finance team members who need billing access without operational permissions. -### Dev role +### Developer role -The dev role extends basic permissions with additional capabilities for active development work. +The developer role extends basic permissions with additional capabilities for active development work. This role includes all basic permissions plus the ability to start, stop, and create Pods. Developers can fully manage computing resources for their work while remaining restricted from billing information and account settings. diff --git a/organizations/org-roles.mdx b/organizations/org-roles.mdx index 7dbdbc758..865ea914b 100644 --- a/organizations/org-roles.mdx +++ b/organizations/org-roles.mdx @@ -4,11 +4,11 @@ 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. +Every member of an organization is assigned one of four built-in roles: admin, billing, developer, 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 | +| Action | Admin | Developer | Billing | Basic | |---|---|---|---|---| | Manage members, groups, and org settings | ✓ | — | — | — | | View member roster | ✓ | ✓ | ✓ | ✓ | @@ -22,7 +22,7 @@ Every member of an organization is assigned one of four built-in roles: admin, b **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. +**Developer.** Full compute access with no billing or member management. Developers 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. diff --git a/organizations/orgs-billing.mdx b/organizations/orgs-billing.mdx index a9254c7a3..dacda2b26 100644 --- a/organizations/orgs-billing.mdx +++ b/organizations/orgs-billing.mdx @@ -10,7 +10,7 @@ Organizations are billed on a post-paid invoice model. Usage from all members ac 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. +Admin and billing roles see usage for all org members. Developer members see their own usage only. ## Cost centers diff --git a/organizations/orgs-overview.mdx b/organizations/orgs-overview.mdx index c12b9da07..e6961b9b3 100644 --- a/organizations/orgs-overview.mdx +++ b/organizations/orgs-overview.mdx @@ -30,7 +30,7 @@ Organizations and Teams are mutually exclusive. Accepting an organization invita **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. +**Roles:** Every member is assigned one of four built-in roles: admin, billing, developer, 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). diff --git a/organizations/orgs-resource-tagging.mdx b/organizations/orgs-resource-tagging.mdx index 102e9ef81..994b0c7b0 100644 --- a/organizations/orgs-resource-tagging.mdx +++ b/organizations/orgs-resource-tagging.mdx @@ -13,7 +13,7 @@ Resource tagging is available to organization accounts only. Tags are key-value - 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. +- Admin and developer roles can create, edit, and delete tags. Basic members can apply existing tags to resources. Billing members can only view tags. ## System tags From f8e3b4b1baaf279a551d2644b80f3b4f6e161bb7 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" Date: Wed, 14 Oct 2026 17:21:22 +0000 Subject: [PATCH 2/2] Limit rename to Organizations and rename Basic to Contributor --- accounts-billing/manage-accounts.mdx | 6 +++--- organizations/org-roles.mdx | 6 +++--- organizations/orgs-overview.mdx | 2 +- organizations/orgs-resource-tagging.mdx | 2 +- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/accounts-billing/manage-accounts.mdx b/accounts-billing/manage-accounts.mdx index 7d197a331..49b326997 100644 --- a/accounts-billing/manage-accounts.mdx +++ b/accounts-billing/manage-accounts.mdx @@ -56,7 +56,7 @@ Your account will gain access to the team's resources based on the role assigned Runpod provides four distinct roles to control access within team accounts. Each role includes specific permissions designed for different responsibilities. -| Permission | Basic | Billing | Developer | Admin | +| Permission | Basic | Billing | Dev | Admin | |------------|-------|---------|-----|-------| | Access team account | ✅ | ✅ | ✅ | ✅ | | Connect to existing Pods | ✅ | ❌ | ✅ | ✅ | @@ -85,9 +85,9 @@ The billing role focuses exclusively on financial management aspects of the acco Users with this role can access all billing information, manage payment methods, and view invoices. They cannot access computing resources, making this role ideal for finance team members who need billing access without operational permissions. -### Developer role +### Dev role -The developer role extends basic permissions with additional capabilities for active development work. +The dev role extends basic permissions with additional capabilities for active development work. This role includes all basic permissions plus the ability to start, stop, and create Pods. Developers can fully manage computing resources for their work while remaining restricted from billing information and account settings. diff --git a/organizations/org-roles.mdx b/organizations/org-roles.mdx index 865ea914b..3229fe274 100644 --- a/organizations/org-roles.mdx +++ b/organizations/org-roles.mdx @@ -4,11 +4,11 @@ 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, developer, or basic. There is no owner role; admin is the highest level. Only org admins can assign or change member roles. +Every member of an organization is assigned one of four built-in roles: admin, billing, developer, or contributor. There is no owner role; admin is the highest level. Only org admins can assign or change member roles. ## Role overview -| Action | Admin | Developer | Billing | Basic | +| Action | Admin | Developer | Billing | Contributor | |---|---|---|---|---| | Manage members, groups, and org settings | ✓ | — | — | — | | View member roster | ✓ | ✓ | ✓ | ✓ | @@ -26,7 +26,7 @@ Every member of an organization is assigned one of four built-in roles: admin, b **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. +**Contributor.** Read and use access to existing resources. Contributors 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 diff --git a/organizations/orgs-overview.mdx b/organizations/orgs-overview.mdx index e6961b9b3..a7b12f20c 100644 --- a/organizations/orgs-overview.mdx +++ b/organizations/orgs-overview.mdx @@ -30,7 +30,7 @@ Organizations and Teams are mutually exclusive. Accepting an organization invita **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, developer, 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. +**Roles:** Every member is assigned one of four built-in roles: admin, billing, developer, or contributor. 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). diff --git a/organizations/orgs-resource-tagging.mdx b/organizations/orgs-resource-tagging.mdx index 994b0c7b0..8c697a82f 100644 --- a/organizations/orgs-resource-tagging.mdx +++ b/organizations/orgs-resource-tagging.mdx @@ -13,7 +13,7 @@ Resource tagging is available to organization accounts only. Tags are key-value - 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 developer roles can create, edit, and delete tags. Basic members can apply existing tags to resources. Billing members can only view tags. +- Admin and developer roles can create, edit, and delete tags. Contributors can apply existing tags to resources. Billing members can only view tags. ## System tags