diff --git a/organizations/org-roles.mdx b/organizations/org-roles.mdx index 7dbdbc75..3229fe27 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 contributor. 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 | Contributor | |---|---|---|---|---| | Manage members, groups, and org settings | ✓ | — | — | — | | View member roster | ✓ | ✓ | ✓ | ✓ | @@ -22,11 +22,11 @@ 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. -**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-billing.mdx b/organizations/orgs-billing.mdx index a9254c7a..dacda2b2 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 903df9ad..270a1341 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/org-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/org-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/orgs-groups). diff --git a/organizations/orgs-resource-tagging.mdx b/organizations/orgs-resource-tagging.mdx index 102e9ef8..8c697a82 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. Contributors can apply existing tags to resources. Billing members can only view tags. ## System tags