> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Identity and access management (IAM)

> CoreWeave's Identity and Access Management system for controlling access to Cloud Platform resources

CoreWeave Identity and Access Management (IAM) controls access to Cloud Platform resources. This page explains how CoreWeave IAM and product-specific controls work together, so you can identify which controls govern access for an identity, credential, resource, and action.

> [!NOTE]
>
> CoreWeave IAM doesn't govern Forge. Forge has a separate identity and access system for organizations, teams, projects, and product access. See [Forge and CoreWeave identity](https://docs.coreweave.com/security/forge-identity-and-access.md).

## Authorization model

Use the following layers to determine how a user or workload gets access:

| Layer | Question it answers | CoreWeave controls |
| - | - | - |
| **Identity and provisioning** | Who is the user or workload? | [Organizations and users](https://docs.coreweave.com/security/authn-authz/orgs-users.md), [Security Assertion Markup Language (SAML) single sign-on (SSO)](https://docs.coreweave.com/security/authn-authz/saml-sso/intro-saml-sso.md), and [Automated User Provisioning (AUP)](https://docs.coreweave.com/security/automated-user-provisioning.md) establish and synchronize users and groups. [SUNK User Provisioning (SUP)](https://docs.coreweave.com/products/sunk/manage_sunk/manage_cluster_access/sunk_user_provisioning.md) extends CoreWeave identities into SUNK clusters. |
| **Credentials and authentication** | How does the identity prove who it is? | Users can authenticate with login credentials or [API access tokens](https://docs.coreweave.com/security/authn-authz/manage-api-access-tokens.md). CoreWeave Kubernetes Service (CKS) supports [managed and unmanaged authentication](https://docs.coreweave.com/products/cks/auth-access/introduction.md). CoreWeave AI Object Storage uses [access keys](https://docs.coreweave.com/products/storage/object-storage/auth-access/manage-access-keys/about.md), including temporary credentials from [Workload Identity Federation (WIF)](https://docs.coreweave.com/products/storage/object-storage/auth-access/workload-identity-federation/about.md). SUNK users authenticate to cluster nodes with SSH keys distributed through SUP. |
| **CoreWeave IAM authorization** | Which Cloud Platform actions can the identity perform? | [IAM Access Policies](https://docs.coreweave.com/security/iam/access-policies.md) assign [IAM roles](https://docs.coreweave.com/security/iam/access-policies/roles.md) to users and groups. CoreWeave IAM uses default-deny authorization: a principal needs an applicable role before it can perform a platform action. |
| **Service-specific authorization** | Which actions can the authenticated identity perform inside the service? | Object Storage uses organization and bucket access policies for S3-compatible operations. CKS uses Kubernetes role-based access control (RBAC) inside clusters. SUNK uses POSIX and Slurm access controls. |

An identity or credential doesn't grant authorization by itself. For example, an API access token authenticates its owner. The owner's IAM roles determine which platform actions they can perform with the token. Service-specific controls can impose additional requirements.

## Service authorization boundaries

The following services have authorization controls outside IAM Access Policies:

| Service | IAM Access Policies | Service-specific authorization |
| - | - | - |
| **Object Storage** | The **Object Storage Admin** role grants access to `cwobject:` control-plane actions. | An [organization access policy](https://docs.coreweave.com/products/storage/object-storage/auth-access/organization-policies/about.md) can grant narrower `cwobject:` permissions, such as `cwobject:CreateAccessKey`. [Organization and bucket access policies](https://docs.coreweave.com/products/storage/object-storage/auth-access/policies.md) govern S3-compatible bucket and object operations. Access keys, including WIF credentials, authenticate requests but don't grant data access by themselves. |
| **CKS** | **CKS Admin** and **CKS Viewer** govern platform-level CKS and virtual private cloud (VPC) actions. | After a user authenticates to the Kubernetes API, Kubernetes role-based access control (RBAC) determines which resources and actions the user can access inside the cluster. |
| **SUNK** | CoreWeave IAM provides the users and groups that SUP can provision. IAM Access Policies don't directly govern access inside a SUNK cluster. | SUP and `nsscache` create POSIX identities and Slurm users. SSH keys authenticate users, while POSIX permissions, Slurm associations, and optional [`pam_slurm_adopt`](https://docs.coreweave.com/products/sunk/manage_sunk/manage_cluster_access/pam-slurm-adopt) controls determine cluster and compute-node access. |

## Enterprise onboarding

When you onboard an organization, use the following sequence to set up identity, provisioning, and least-privilege access:

1. **Sign-in and SSO**: Configure SAML SSO so your team signs in through your identity provider. To enforce SSO as the only sign-in method, use [login methods](https://docs.coreweave.com/security/authn-authz/login-methods.md) to turn off email and password, Google, and GitHub sign-in by default, and review per-user overrides.
2. **Multi-factor authentication (MFA)**: Each user can enable two-factor authentication (2FA) with a time-based one-time password (TOTP) on their [account settings](https://console.coreweave.com/account/settings) page. For organization-wide enforcement, configure your identity provider to require MFA on every SSO sign-in. See [Can I enforce 2FA for all users?](https://docs.coreweave.com/support/platform/articles/can-i-enforce-2fa-for-all-users).
3. **User and group provisioning**: Sync users and groups from your identity provider with Automated User Provisioning (AUP), which uses the System for Cross-domain Identity Management (SCIM). Group memberships are synchronized with IAM and can be used in access policies.
4. **Least-privilege access**: Assign IAM roles through access policies. Use [default access policies](https://docs.coreweave.com/security/iam/access-policies.md#default-access-policies) to keep common access patterns current as CoreWeave introduces new roles, and create custom policies for narrower access.

Together, these controls establish organization-wide sign-in, user provisioning, and least-privilege IAM access.

### Per-cluster access scoping

[Managed Authentication](https://docs.coreweave.com/products/cks/auth-access/managed-auth/kubeconfig.md) allows every CoreWeave user in an organization to authenticate to every CKS cluster in that organization. IAM roles determine what each user can do, but they don't provide per-cluster scoping. To control which identities can authenticate to a specific cluster, configure [Unmanaged Authentication](https://docs.coreweave.com/products/cks/auth-access/unmanaged-auth/introduction.md) with your own identity provider. Then, use Kubernetes RBAC to authorize those identities. For stronger organizational separation, [contact support](https://docs.coreweave.com/support/contact.md) about using multiple organizations. See [How do I scope users to specific clusters?](https://docs.coreweave.com/support/platform/articles/how-do-i-scope-users-to-specific-clusters).

### Object Storage access without admin

To obtain Object Storage credentials, users need either the **Object Storage Admin** role or an organization access policy that grants the narrower `cwobject:CreateAccessKey` permission. To let users obtain credentials without the full admin role, grant this permission through an organization access policy. Users can then [exchange their API access token directly for temporary credentials](https://docs.coreweave.com/products/storage/object-storage/auth-access/manage-access-keys/api-access-token.md). Combine this approach with [group-based bucket policies](https://docs.coreweave.com/products/storage/object-storage/auth-access/bucket-access/bucket-policies.md) so SCIM group memberships control which buckets each user can access.

For production workloads, CoreWeave recommends that you use Workload Identity Federation to exchange short-lived identity-provider tokens for temporary credentials.

## Troubleshoot access

Start with the layer where the access attempt failed:

* If a user can't sign in or obtain an API access token, see the [authentication and access support articles](https://docs.coreweave.com/support/platform/tags/authentication-access.md).
* If CKS returns an authentication or authorization error, see [Managed Authentication errors](https://docs.coreweave.com/products/cks/auth-access/managed-auth/kubeconfig.md#authentication-errors).
* If a user can't create Object Storage credentials or access a bucket, see [How do I give someone Object Storage access without admin privileges?](https://docs.coreweave.com/support/storage/articles/how-do-i-give-someone-object-storage-access-without-admin-privileges).
* If Grafana doesn't show metrics, see [Why are my metrics missing in Grafana?](https://docs.coreweave.com/support/observability/articles/why-are-my-metrics-missing-in-grafana).
* If a SUNK user can't access a cluster, see [How do I add users to the `slurm-users` group?](https://docs.coreweave.com/support/sunk/articles/how-do-i-add-users-to-the-slurm-users-group) and [Where do I add my SSH public key?](https://docs.coreweave.com/support/sunk/articles/where-do-i-add-my-ssh-public-key).

## Next steps

To create an access policy, see [Manage IAM Access Policies](https://docs.coreweave.com/security/iam/access-policies/manage.md).
