diff --git a/accounts-billing/manage-accounts.mdx b/accounts-billing/manage-accounts.mdx index 8d8726b0..2c0157de 100644 --- a/accounts-billing/manage-accounts.mdx +++ b/accounts-billing/manage-accounts.mdx @@ -1,129 +1,44 @@ --- title: "Manage accounts" -description: "Create accounts, manage teams, and configure user permissions in Runpod. Review account, billing, and management details for Runpod." +sidebarTitle: "Manage accounts" +description: "Learn about Runpod account types: personal accounts, teams, and organizations. Understand which account type fits your collaboration needs." --- -To access Runpod resources, you need to either create your own account or join an existing team through an invitation. This guide explains how to set up and manage accounts, teams, and user roles. +Runpod supports three account types: personal accounts, teams, and organizations. Choose the type that fits how you and your collaborators work. -## Create an account +## Personal accounts -Sign up for a Runpod account at [console.runpod.io/signup](https://www.console.runpod.io/signup). +A personal account is the default account type. Sign up at [console.runpod.io/signup](https://console.runpod.io/signup) to get started. All resources you deploy, including Pods, Serverless endpoints, and network volumes, belong to your personal account. -Once created, you can use your account to deploy Pods, create Serverless endpoints, and access other Runpod services. Personal accounts can be converted to team accounts at any time to enable collaboration features. +## Teams -## Convert to a team account +Teams let multiple users collaborate under a shared account with role-based access control. -Team accounts enable multiple users to collaborate on projects and share resources. +For details on setting up and managing a team, see [Manage teams](/teams/manageteams). -To convert your personal account into a team account: +## Organizations -1. Navigate to the [Team page](https://www.console.runpod.io/team) in the Runpod console. -2. Select **Convert to a Team Account**. -3. Enter a team name and confirm the conversion. +Organizations are provisioned accounts for companies and larger teams. - - -You can revert your account back to a personal account at any time. To revert, scroll to the bottom of the [Team page](https://www.console.runpod.io/team) and select **Delete Team**. - - - -## Invite team members - -Team accounts can invite new members to collaborate. Each invitation includes a specific role that determines the member's permissions. - -Create Team Invite dialog showing role selection and required email field - -To invite a new member: - -1. Navigate to the [Team page](https://www.console.runpod.io/team) in the Runpod console. -2. In the **Members** section, select **Invite New Member**. -3. Choose [the appropriate role](#roles-and-permissions) for the new member. -4. Enter the email address of the person you want to invite and click **Create Invite**. -5. Copy the generated invitation link from the **Pending Invites** section and share it with the person you want to invite. - -Invitation links remain active until used or manually revoked. You can view all pending invitations in the team management interface. - -## Join a team - -When invited to join a team, you'll receive an invitation link from a team member. To accept: - -1. Click the invitation link provided by the team member. -2. Select **Join Team** to accept the invitation. - -Your account will gain access to the team's resources based on the role assigned to you. - -## Roles and permissions - -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 | -|------------|-------|---------|-----|-------| -| Access team account | ✅ | ✅ | ✅ | ✅ | -| Connect to existing Pods | ✅ | ❌ | ✅ | ✅ | -| Create/delete/start/stop Pods | ❌ | ❌ | ✅ | ✅ | -| Create/delete Serverless endpoints | ❌ | ❌ | ✅ | ✅ | -| Send requests to Serverless endpoints | ✅ | ❌ | ✅ | ✅ | -| Connect to existing Instant Clusters | ✅ | ❌ | ✅ | ✅ | -| Create/delete/start/stop Instant Clusters | ❌ | ❌ | ❌ | ✅ | -| Create/update/delete network volumes | ❌ | ❌ | ✅ | ✅ | -| View billing information | ❌ | ✅ | ❌ | ✅ | -| Manage payment methods | ❌ | ✅ | ❌ | ✅ | -| Invite team members | ❌ | ❌ | ❌ | ✅ | -| Manage team permissions | ❌ | ❌ | ❌ | ✅ | -| Modify team account settings | ❌ | ❌ | ❌ | ✅ | -| Access audit logs | ❌ | ❌ | ❌ | ✅ | - -### Basic role - -The basic role provides essential access for users who need to work with existing resources without management capabilities. - -This role allows users to access the team account and connect to already-deployed computing resources (e.g., Pods and Serverless endpoints) for development work. Users with this role cannot view billing information, start or stop Pods, or create new resources. - -### Billing role - -The billing role focuses exclusively on financial management aspects of the account. - -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 - -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. - -### Admin role - -The admin role provides complete control over all account features and settings. - -Administrators have unrestricted access to manage team members, configure account settings, handle billing, and control all team computing resources. This role should be reserved for team leaders and trusted members who need full account access. +For details on how organizations work, see [Organizations](/organizations/orgs-overview). ## Account spend limits -By default, Runpod accounts have a spend limit of \$80 per hour across all resources. This limit protects your account from unexpected charges. If your workload requires higher spending capacity, you can [contact support](https://www.runpod.io/contact) to increase it. +By default, Runpod accounts have a spend limit of $80 per hour across all resources. This protects your account from unexpected charges. To increase the limit, [contact support](https://www.runpod.io/contact). ## Monitor account activity -Runpod provides comprehensive audit logs to track all actions performed within your account. This feature helps maintain security and accountability across team operations. +Runpod provides comprehensive audit logs to track all actions performed within your account. This feature helps maintain security and accountability across your operations. -Access audit logs at [console.runpod.io/user/audit-logs](https://www.console.runpod.io/user/audit-logs). +Access audit logs at [console.runpod.io/user/audit-logs](https://console.runpod.io/user/audit-logs). The audit system records detailed information about each action, including the user who performed it, the affected resource, and the timestamp. You can filter logs by date range, user, resource type, resource ID, and specific actions to investigate account activity or troubleshoot issues. -Regular review of audit logs helps identify unusual activity and ensures team members use resources appropriately. - -## Best practices - -When managing team accounts, establish clear role assignments based on each member's responsibilities. Regularly review team membership and remove access for members who no longer need it. - -For enhanced security, use the principle of least privilege by assigning the minimum role necessary for each team member's work. Consider creating separate accounts for billing management to isolate financial access from technical operations. - -Monitor audit logs periodically to ensure compliance with your organization's policies and identify any unauthorized activities early. +Regular review of audit logs helps identify unusual activity and ensures resources are being used appropriately. ## Next steps -After setting up your account and team you can: - -* [Create API keys](/get-started/api-keys) to enable programmatic access to Runpod services. -* [Deploy your first Pod](/get-started) to start using GPU resources. -* Configure [Serverless endpoints](/serverless/overview) for scalable AI inference. -* Set up [billing and payment methods](https://console.runpod.io/user/billing) for your team. \ No newline at end of file +- [Manage teams](/teams/manageteams) to invite members and assign roles. +- [Organizations](/organizations/orgs-overview) for enterprise billing and resource management. +- [Create API keys](/get-started/api-keys) for programmatic access to Runpod services. +- [Set up billing](/accounts-billing/billing) to manage payment methods and view usage. diff --git a/docs.json b/docs.json index f01e4fd7..b74494e1 100644 --- a/docs.json +++ b/docs.json @@ -287,6 +287,13 @@ "accounts-billing/add-tax-id" ] }, + { + "group": "Teams", + "pages": [ + "teams/manageteams", + "teams/teamroles" + ] + }, { "group": "Organizations (Beta)", "pages": [ diff --git a/teams/manageteams.mdx b/teams/manageteams.mdx new file mode 100644 index 00000000..edf63b32 --- /dev/null +++ b/teams/manageteams.mdx @@ -0,0 +1,63 @@ +--- +title: "Manage teams" +sidebarTitle: "Manage teams" +description: "Create and manage team accounts in Runpod. Invite members, assign roles, and collaborate on Pods, endpoints, and other resources." +--- + +Teams let multiple users collaborate on Runpod resources under a shared account. Any personal account can be converted to a team account to enable member management and role-based access control. + +## Create a team account + + + + Navigate to **Create team** in the [Runpod console](https://console.runpod.io/team). + + + Click **Convert to a Team Account**. Enter a team display name, check the acknowledgment checkbox, and click **Convert to a Team Account** to confirm. + + + + +To delete your team, scroll to the bottom of the **Team** page and click **Delete Team**. This reverts your account to a personal account. All members are removed, but your resources remain unchanged. + + +## Invite team members + +Only admins can invite new members. Each invitation is tied to a specific email address and can only be accepted by the user with that address. + + + + Go to the [Team page](https://console.runpod.io/team) in the Runpod console. + + + In the **Members** section, click **Invite new member**. Select a role, enter the member's email address, and click **Create Invite**. + + + The invitation link appears under **Pending Invites**. Copy it and share it with the invitee, or they will receive an email with a direct link to accept. + + + +To invite multiple members at once, click **Bulk Invite**. Upload a CSV file or paste content directly using the format `role,email`, one member per line. A header row is detected automatically. Click **Send Invites** when done. + +Invitation links remain active until used or manually revoked. + +## Join a team + +When invited to a team, you'll receive an invitation link from an admin. + + + + Click the link provided by the team admin. + + + Select **Join Team** to accept. + + + +Your account gains access to the team's resources based on the role assigned to you. + +## Next steps + +- [Create API keys](/get-started/api-keys) for programmatic access to Runpod services. +- [Deploy a Pod](/pods/manage-pods) to start using GPU resources. +- [Set up Serverless endpoints](/serverless/overview) for scalable AI inference. diff --git a/teams/teamroles.mdx b/teams/teamroles.mdx new file mode 100644 index 00000000..30e192e4 --- /dev/null +++ b/teams/teamroles.mdx @@ -0,0 +1,40 @@ +--- +title: "Roles and permissions" +sidebarTitle: "Roles and permissions" +description: "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 | ✅ | ❌ | ✅ | ✅ | +| 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 | ❌ | ❌ | ✅ | ✅ | +| 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 and send requests to Serverless endpoints, but cannot create resources, view billing, or change account settings. + +## Billing + +The Billing role is for financial management only. Billing members can view billing information and manage payment methods but have no access to compute resources. + +## Dev + +The Dev role extends Basic with full compute resource management. Dev members can create, start, stop, and delete Pods, Serverless endpoints, and network volumes, 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.