docs: rename Teams to Projects (+ new Projects page)#306
Open
beran-t wants to merge 2 commits into
Open
Conversation
Renames the "Teams" concept to "Projects" across user-facing prose and adds a new docs/projects.mdx concept page. - New page: docs/projects.mdx (Getting started nav) explaining what a project owns (API keys, sandboxes, templates, billing) plus a note that Teams was the former name. - Rename conceptual prose and illustrative slug placeholders (your-team-slug -> your-project-slug) in billing, byoc, template names/tags/caching/base-image, public-templates FAQ, access-token migration, and sandbox lifecycle pages. Left literal API/env identifiers unchanged (E2B_TEAM_ID, teamId, sandboxTeamId, sandbox_team_id) since those are part of the actual API surface and were not stated to change. See PR description.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
tvi
reviewed
Jul 21, 2026
| icon: "folder" | ||
| --- | ||
|
|
||
| A **project** is the workspace under your E2B account that owns everything you build: API keys, sandboxes, templates, and billing. Every sandbox you create runs inside a project, and every API key is scoped to exactly one project, so the key you use determines which project's resources and limits apply. |
There was a problem hiding this comment.
@beran-t what about
A project groups the resources you build with under your E2B account — API keys, sandboxes, templates, and billing. Every sandbox runs inside a project, and every API key is scoped to exactly one project, so the key you use determines which project's resources and limits apply.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Per the Teams → Projects rename, this:
docs/projects.mdx(under Getting started, after API key) explaining what a project is and what it owns: API keys, sandboxes, templates, and billing/limits. Includes an<Info>note that projects were formerly called Teams and existing keys/slugs keep working.billing.mdx,byoc.mdx,template/caching.mdx,template/base-image.mdx,template/tags.mdx,template/names.mdx(incl. the "Team-local naming" heading)faq/public-templates.mdx(title + body)migration/access-token-deprecation.mdxsandbox/lifecycle-events-api.mdx,sandbox/lifecycle-events-webhooks.mdx(prose + comments)your-team-slug/team-slug/template-name→your-project-slug/project-slug/template-nameDeliberately NOT changed (needs product confirmation)
I left literal API/env identifiers as-is, because the Slack ask was a rename of the concept, not a stated change to the API surface. Renaming these in docs would misdocument the actual product unless the API is also changing:
E2B_TEAM_IDenv var (sandbox/environment-variables.mdx)teamId/sandboxTeamId/sandbox_team_idfields in webhook/API response payloadsQuestion for review: are any of these API-level identifiers also being renamed? If so, I'll follow up. Also left untouched: incidental non-concept uses like "our support team" and "deploying for your team," plus the unrelated Microsoft Teams / Teamwork MCP entries.