Roles and permissions

Understand the four built-in team roles in Runpod: Admin, Billing, Dev, and Basic. Learn what each role can access and manage.

Teams have four built-in roles. Each role is designed for a specific set of responsibilities and grants access accordingly. Assign the minimum role necessary for each member’s work, and review team membership regularly to remove access for members who no longer need it.

Permission	Basic	Billing	Dev	Admin
Access team account	✅	✅	✅	✅
Connect to existing Pods	✅	❌	✅	✅
View Pods and compute resources	❌	✅	✅	✅
Create, delete, start, and stop Pods	❌	❌	✅	✅
Create and delete Serverless endpoints	❌	❌	✅	✅
Send requests to Serverless endpoints	✅	❌	✅	✅
Connect to existing Instant Clusters	✅	❌	✅	✅
Create, delete, start, and stop Instant Clusters	❌	❌	✅	✅
Create, update, and delete network volumes	❌	❌	✅	✅
Manage container registry credentials	❌	❌	✅	✅
Manage SSH keys	✅	❌	✅	✅
View billing information	❌	✅	❌	✅
Manage payment methods	❌	✅	❌	✅
Invite team members	❌	❌	❌	✅
Manage team permissions	❌	❌	❌	✅
Modify team account settings	❌	❌	❌	✅
Access audit logs	✅	✅	✅	✅

Basic

The Basic role provides access to the team account and existing compute resources. Basic members can connect to running Pods, send requests to Serverless endpoints, and manage SSH keys, but cannot create resources, view billing, or change account settings.

Billing

The Billing role is for financial management. Billing members can view billing information and manage payment methods. They can also view compute resources such as Pods, endpoints, and network volumes in order to understand spend, but cannot create, modify, or connect to them.

Dev

The Dev role extends Basic with full compute resource management. Dev members can create, start, stop, and delete Pods, Serverless endpoints, Instant Clusters, and network volumes. They can also manage container registry credentials used by Pods and Serverless workers to pull private images, but cannot access billing or account settings.

Admin

The Admin role has complete control over the team. Admins can manage members, configure account settings, handle billing, and control all compute resources.

Next steps

• Manage teams to invite members and assign roles.
• Create API keys for programmatic access to Runpod services.
• Deploy a Pod to start using GPU resources.