Create teams.overview by lavanya-gunreddi · Pull Request #851 · runpod/docs

lavanya-gunreddi · 2026-09-21T15:23:21Z

No description provided.

mintlify · 2026-09-21T15:23:24Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
runpod-docs	🟢 Ready	View Preview	Sep 24, 2026, 2:43 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

rambo-runpod

Checked the content against the backend (runpod/RunPod origin/main, 2da6af24c) and the console (main-ui origin/main, ff9b7114e).

Structure is good and needs no change: putting Teams as a peer of Accounts and billing and Organizations (Beta) matches how Organizations is already set up, a top-level teams/ directory matches repo layout, and every link target resolves. Not renaming it "Teams (Beta)" is also right, since teams are GA.

Findings are content accuracy, inline below. Six are wrong against the current backend; the rest are consistency and link-integrity items.

Heads-up on two of them: I have a backend PR open (runpod/RunPod#6176) that changes team role verdicts for audit logs and the Billing role. I have flagged which comments it affects so this page does not get written twice.

rambo-runpod · 2026-09-21T22:57:13Z

+| Create and delete Serverless endpoints | ❌ | ❌ | ✅ | ✅ |
+| Send requests to Serverless endpoints | ✅ | ❌ | ✅ | ✅ |
+| Connect to existing Instant Clusters | ✅ | ❌ | ✅ | ✅ |
+| Create, delete, start, and stop Instant Clusters | ❌ | ❌ | ❌ | ✅ |


Dev should be white-check, not cross.

Team Dev holds CLUSTER_MANAGE (model/src/authz/roleGrid.ts:511), and cluster create/delete/update/expand gate on CLUSTER:CREATE/DELETE/UPDATE (node/graphql/schema/cluster.ts:276,286,289). The console agrees: cluster delete is [ADMIN, DEV] (features/Clusters/ClusterCard/index.tsx:57).

rambo-runpod · 2026-09-21T22:57:13Z

+
+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.


Wrong: team invites expire after 3 days.

const expiresAt = addDays(now, 3) (model/src/team/createTeamInvite.ts:74, and the bulk path at createBulkTeamInvites.ts:121), enforced on accept (joinTeam.ts:26, "This invite has expired.").

You may be thinking of org invites, which are 14 days. The constant says so explicitly: // Org invites expire after 14 days (longer than TeamInvite's 3-day window...) (model/src/org/invite/constants.ts:1-3).

Suggested change

Invitation links remain active until used or manually revoked.

Invitation links expire 3 days after they are created. They also become invalid once used or manually revoked.

rambo-runpod · 2026-09-21T22:57:13Z

+</Steps>
+
+<Note>
+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.


Deleting a team is owner-only, not admin.

if (teamToDelete.ownerId !== context.auth.originalUserId) throw 'Only the team owner can delete the team.' (model/src/team/deleteTeam.ts:27-28). A team admin who is not the owner cannot do this.

Two other omissions: clicking Delete Team opens a confirmation dialog, and pending invites are cancelled along with memberships (TeamInvite.team ... onDelete: Cascade).

Suggested change

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.

Only the team owner can delete a team. To do so, scroll to the bottom of the **Team** page, click **Delete Team**, and confirm in the dialog. This reverts your account to a personal account. All members are removed and any pending invites are cancelled, but your resources remain unchanged.

rambo-runpod · 2026-09-21T22:57:13Z

+## 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.


Please keep an explicit ## Create an account heading here.

24 pages link to /accounts-billing/manage-accounts specifically as the signup prerequisite, for example:

serverless/quickstart.mdx:15 - "You've created a Runpod account"

tutorials/migrations/openai/overview.mdx:11 - "Create a Runpod account"

public-endpoints/quickstart.mdx:14 - "A Runpod account with at least 1 dollar in credits"

The signup URL does survive inside this paragraph, so nothing 404s, but those readers arrive at an account-types explainer rather than instructions, and the #create-an-account anchor is gone. Re-adding the H2 preserves the anchor and fixes all 24 in one edit.

While here: docs.json:1683 redirects /docs/invites to this page, which existed to serve the invite content this PR moved. It should now point at the teams page. release-notes.mdx:432 links "Teams: ... role-based access control" here too, and wants the roles page.

@Promptless work on this comment

rambo-runpod · 2026-09-21T22:57:13Z

+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).


teams/teamroles is in the sidebar but nothing in the repo links to it in prose, so the only way to find it is scanning the nav. Worth linking from here, and from the invite step on the Manage teams page where a reader picks a role.

Suggested change

For details on setting up and managing a team, see [Manage teams](/teams/manageteams).

For details on setting up and managing a team, see [Manage teams](/teams/manageteams). For what each role can do, see [Roles and permissions](/teams/teamroles).

@Promptless work on this comment

rambo-runpod · 2026-09-21T22:57:13Z

+    Go to the [Team page](https://console.runpod.io/team) in the Runpod console.
+  </Step>
+  <Step title="Send the invitation">
+    In the **Members** section, click **Invite new member**. Select a role, enter the member's email address, and click **Create Invite**.


The team-invite screenshot from the old page (create-team-invite-dialog-d8cb3fc6.png, "Create Team Invite dialog showing role selection and required email field") was removed and not re-added anywhere. This step is where it belongs. Confirmed it appears nowhere on the branch.

rambo-runpod · 2026-09-21T22:57:13Z

+
+<Steps>
+  <Step title="Open the Team page">
+    Navigate to **Create team** in the [Runpod console](https://console.runpod.io/team).


Minor: this step is titled "Open the Team page" but the body says to navigate to Create team. The second Steps block at line 29-30 says "Go to the Team page", which reads better. Both labels are real; the sidebar entry is "Create team" for a personal account and "Team" once you are on a team (routes.tsx:187-201). Worth making the title and body agree.

Also verified and correct as written: the Convert to a Team Account button and modal, the team display name field, and the acknowledgment checkbox, which does gate the confirm button.

Two undocumented limits you may want to mention: team names must be 3 to 50 characters, and a user can own only one team (createTeam.ts:10-26, "You can only have 1 team").

Co-authored-by: rambo wu <rambo.wu@runpod.io>

promptless · 2026-09-24T13:28:12Z

Thanks for reviewing the teams overview page — we have your feedback and are working through it now. We'll follow up here on the PR once the updates are ready.

- Restore '## Create an account' heading to preserve the #create-an-account anchor and land the ~24 inbound signup links on instructions - Link Roles and permissions from the Teams section; fix broken /teams/manageteams links to /teams/manage-teams - Correct spend-limit description to match enforcement (compute-only, checked at deploy/resume, running resources unaffected); restore $ escape - Correct audit-log filter list to match the API (date range, action, free-text; user filter is organization-only) and note export formats - Point /docs/invites redirect and release-notes Teams link at the relocated teams pages

promptless · 2026-09-24T13:38:14Z

Thanks for the detailed review, @lavanya-gunreddi. All four points are addressed in commit c8fb9b5 on this branch.

Create an account heading: Restored a ## Create an account H2, so the #create-an-account anchor is preserved and the pages that link here for signup still land on the instructions. Also updated the /docs/invites redirect and the release notes Teams link to point at the relocated /teams/manage-teams and /teams/team-roles pages.
Roles and permissions link: Added a Roles and permissions link from the Teams section. The suggested paths had a typo, so I used the live routes /teams/manage-teams and /teams/team-roles, and fixed two existing broken /teams/manageteams links on the page.
Spend limit: Reworded to match the actual enforcement (it caps compute, is checked at deploy and resume, and does not affect already-running resources), and restored the escaped \$. One thing to confirm: you noted that postpaid accounts bypass the limit entirely. The current wording follows your suggestion and does not mention that, so postpaid readers may still read "deploys are blocked" as applying to them. Do you want me to add the postpaid exception?
Audit-log filters: Corrected the filter list to the API-supported set (date range, action, and free-text search, with the user filter available at the organization level), and added the note that logs export as CSV, JSON, or XML.

Create teams.overview

7fe76b2

mintlify Bot deployed to staging September 21, 2026 15:24 View deployment

Update teams.overview

a430595

mintlify Bot deployed to staging September 21, 2026 15:57 View deployment

Create teams.roles

113d046

mintlify Bot deployed to staging September 21, 2026 16:01 View deployment

Rename teams.overview to manageteams.mdx

c4ea94b

mintlify Bot deployed to staging September 21, 2026 16:09 View deployment

Rename teams.roles to teamroles.mdx

1718cea

mintlify Bot deployed to staging September 21, 2026 16:09 View deployment

Update manage-accounts.mdx

5483b52

mintlify Bot deployed to staging September 21, 2026 16:27 View deployment

Update docs.json

3824a39

mintlify Bot deployed to staging September 21, 2026 16:29 View deployment

rambo-runpod reviewed Sep 21, 2026

View reviewed changes

Update manageteams.mdx

68e3158

mintlify Bot deployed to staging September 24, 2026 13:12 View deployment

Rename manageteams.mdx to manage-teams.mdx

77860d1

mintlify Bot deployed to staging September 24, 2026 13:15 View deployment

Rename teamroles.mdx to team-roles.mdx

0f2c3bf

mintlify Bot deployed to staging September 24, 2026 13:16 View deployment

Update team-roles.mdx

cd8e122

mintlify Bot deployed to staging September 24, 2026 13:18 View deployment

Apply suggestion from @rambo-runpod

e119d75

Co-authored-by: rambo wu <rambo.wu@runpod.io>

mintlify Bot deployed to staging September 24, 2026 13:25 View deployment

Update docs.json

2580c68

mintlify Bot deployed to staging September 24, 2026 13:27 View deployment

Merge branch 'main' into lg-teams

23c0a32

mintlify Bot deployed to staging September 24, 2026 13:28 View deployment

mintlify Bot deployed to staging September 24, 2026 13:37 View deployment

Update team-roles.mdx

26cdbfe

mintlify Bot deployed to staging September 24, 2026 14:43 View deployment


		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.

	Invitation links remain active until used or manually revoked.
	Invitation links expire 3 days after they are created. They also become invalid once used or manually revoked.

	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.
	Only the team owner can delete a team. To do so, scroll to the bottom of the Team page, click Delete Team, and confirm in the dialog. This reverts your account to a personal account. All members are removed and any pending invites are cancelled, but your resources remain unchanged.

	For details on setting up and managing a team, see [Manage teams](/teams/manageteams).
	For details on setting up and managing a team, see [Manage teams](/teams/manageteams). For what each role can do, see [Roles and permissions](/teams/teamroles).

Conversation

lavanya-gunreddi commented Sep 21, 2026

Uh oh!

mintlify Bot commented Sep 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rambo-runpod left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

promptless Bot commented Sep 24, 2026

Uh oh!

promptless Bot commented Sep 24, 2026

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

mintlify Bot commented Sep 21, 2026 •

edited

Loading