These roles apply to CoreWeave Infrastructure, not Forge. Forge roles belong to a separate identity and access system. See Forge and CoreWeave identity.
Access control and IAM
These roles manage identities, groups, access policies, and personal access tokens.On 2026-10-07, the Access Token Admin role was renamed to Access Token User. Only the display name changed. The role still lets users create and delete their own API access tokens, subject to organization policy.
CKS clusters
These roles manage CoreWeave Kubernetes Service clusters and VPC resources.Inference
These roles manage inference gateways, deployments, capacity claims, and hot-loads.Sandbox
These roles manage CoreWeave Sandboxes profiles, runners, and sandbox execution.Bare metal
These roles manage the CoreWeave Bare Metal Service (limited availability), including BMC serial console access to nodes. Contact support to request access.Object storage
The Object Storage Admin role’s scope hasn’t changed. It has always governed CoreWeave AI Object Storage control-plane actions in the Object Storage API, not bucket or object operations through the S3-compatible API. Access to buckets and objects is governed separately by organization and bucket access policies.Observability and telemetry
These roles cover organization custom dashboards, observability data, and Telemetry Relay configuration. Dashboard permissions are separate from access to metrics and logs. The Grafana Dashboard roles apply to your organization’s custom dashboards and don’t control access to CoreWeave-provided dashboards.Billing
This role grants read-only access to billing data.Notifications and integrations
These roles manage alert subscriptions and the destinations that receive them.Support
This role grants read-only access to support records.
Administrators can manage resources in the Cloud Console, the API, and with infrastructure-as-code (IaC) tools like Terraform.
Legacy group role assignments
Before IAM Access Policies, user permissions were determined by the legacy group a user belonged to. The following table shows how each legacy group maps to the new IAM roles:
Roles added for newer platform features may not be automatically included in legacy admin policies. If you expect access to a feature but can’t reach it, check your organization’s access policies and add the relevant role if it’s missing.
You can review and modify these role assignments or create new groups with different role combinations using IAM Access Policy management.
Next steps
- Learn about IAM Access Policies.
- Create an IAM Access Policy.