From a0e243349649f32262cd62341ab2362e98f91b4e Mon Sep 17 00:00:00 2001 From: "warp-agent-staging[bot]" <240773466+warp-agent-staging[bot]@users.noreply.github.com> Date: Wed, 9 Sep 2026 23:11:25 +0000 Subject: [PATCH 1/7] docs: document Warp's native workspaces model (REV-2397) Co-Authored-By: Warp --- .agents/references/terminology.md | 5 ++ .../support-and-resources/billing.mdx | 2 + .../team-management/admin-panel.mdx | 6 +- .../team-management/roles-and-permissions.mdx | 5 ++ .../docs/enterprise/team-management/teams.mdx | 5 +- .../enterprise/team-management/workspaces.mdx | 84 +++++++++++++++++++ .../admin-panel.mdx | 2 + .../knowledge-and-collaboration/teams.mdx | 6 +- src/sidebar.ts | 1 + 9 files changed, 111 insertions(+), 5 deletions(-) create mode 100644 src/content/docs/enterprise/team-management/workspaces.mdx diff --git a/.agents/references/terminology.md b/.agents/references/terminology.md index 0344575aa..927f4dd8a 100644 --- a/.agents/references/terminology.md +++ b/.agents/references/terminology.md @@ -143,6 +143,11 @@ For the summary of the most critical terms (core features, Automation Platform t - **Workflow** / **Workflows** — Saved, runnable workflows in Warp Drive (often multi-step command sequences). +## Team and workspace terms + +- **workspace** — Warp's top-level organizational unit for enterprise accounts. It groups one or more teams under a single company account, with its own roles (member/admin/owner), billing, and governance settings. See [Workspaces](/enterprise/team-management/workspaces/). + *Usage note:* Lowercase common noun, like "team." Distinct from two other uses of the word: the per-team shared workspace in **Warp Drive** ("teams share a dedicated workspace in Warp Drive"), and a **Slack workspace**, which is a separate company account in Slack. When the surrounding context doesn't already make clear which "workspace" is meant, say so explicitly (e.g. "your Warp workspace" or "your Slack workspace"). + ## Automation Platform terminology Renamed from "Oz" on 2026-08-18. Two surfaces keep the Oz name until 2026-10-06 diff --git a/src/content/docs/enterprise/support-and-resources/billing.mdx b/src/content/docs/enterprise/support-and-resources/billing.mdx index c7af7fb19..1c2c4a7f6 100644 --- a/src/content/docs/enterprise/support-and-resources/billing.mdx +++ b/src/content/docs/enterprise/support-and-resources/billing.mdx @@ -76,6 +76,8 @@ Spending is tracked across all payment types (add-on credits, pay-as-you-go usag Team-wide spending limits (cloud, local, and total) are also available on Warp's self-serve paid plans through admin-managed Add-on credit settings. **Per-user spending limits are Enterprise-only.** For deeper visibility into how individual users consume credits, see the [Enterprise Analytics API](/enterprise/enterprise-features/analytics-api/). ::: +On an Enterprise account whose workspace holds multiple teams, an optional workspace-level cap can sit above these team-level limits — see [Workspace spend limits](/enterprise/team-management/workspaces/#workspace-spend-limits). + #### Monthly spend alerts Warp sends alerts to administrators as team usage approaches each configured spending limit, so you can adjust caps, purchase more credits, or communicate with your team before agent usage is blocked at the cap. diff --git a/src/content/docs/enterprise/team-management/admin-panel.mdx b/src/content/docs/enterprise/team-management/admin-panel.mdx index 896571486..c4f500901 100644 --- a/src/content/docs/enterprise/team-management/admin-panel.mdx +++ b/src/content/docs/enterprise/team-management/admin-panel.mdx @@ -53,6 +53,8 @@ Team members see organization-enforced settings in their personal Settings panel The Admin Panel uses a three-tier enforcement model that keeps administrators in control while allowing appropriate flexibility. +On an Enterprise account whose workspace holds multiple teams, many of these settings are configured once at the workspace level and either enforced or delegated to each team, rather than configured per team as described below — see [Workspace settings and team settings](/enterprise/team-management/workspaces/#workspace-settings-and-team-settings). + ### Setting enforcement levels **Organization enforced** @@ -240,7 +242,7 @@ For Enterprise plans with negotiated credit pools: * Monitor usage by team * Set per-team spending limits -Contact your account manager to configure advanced credit allocation. +Contact your account manager to configure advanced credit allocation. On a multi-team workspace, an optional workspace-level spend cap can also sit above these team-level limits — see [Workspace spend limits](/enterprise/team-management/workspaces/#workspace-spend-limits). ### Sharing settings @@ -319,7 +321,7 @@ After purchasing a Warp enterprise plan: 5. **Configure BYOLLM** (optional) - Route inference through your cloud accounts. 6. **Create shared resources** - Populate team Warp Drive with Workflows, Rules, and Prompts. -See [Roles and permissions](/enterprise/team-management/roles-and-permissions/) for details on user roles and access controls. +See [Roles and permissions](/enterprise/team-management/roles-and-permissions/) for details on user roles and access controls, and [Workspaces](/enterprise/team-management/workspaces/) if your account manages more than one team. ### Adjusting policies for different teams diff --git a/src/content/docs/enterprise/team-management/roles-and-permissions.mdx b/src/content/docs/enterprise/team-management/roles-and-permissions.mdx index 3481d0976..9ee2dc656 100644 --- a/src/content/docs/enterprise/team-management/roles-and-permissions.mdx +++ b/src/content/docs/enterprise/team-management/roles-and-permissions.mdx @@ -7,6 +7,10 @@ description: >- Warp uses a role-based access model to control what team members can do within your organization. Admins manage team settings and enforce policies, while members use Warp's features within the boundaries admins define. +:::note +On an Enterprise account whose workspace holds multiple teams, a company-wide workspace role (member, admin, or owner) sits above the team roles described here — see [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). +::: + ## User roles Warp has three user roles: @@ -72,5 +76,6 @@ For organizations with sensitive internal processes, disable public link sharing ## Related resources +* [Workspaces](/enterprise/team-management/workspaces/) - How the workspace-level role sits above team roles on a multi-team Enterprise account * [Admin Panel](/enterprise/team-management/admin-panel/) - Configure team settings and enforce policies * [Getting started for developers](/enterprise/getting-started/getting-started-developers/) - Developer onboarding guide diff --git a/src/content/docs/enterprise/team-management/teams.mdx b/src/content/docs/enterprise/team-management/teams.mdx index dd2a6e5ca..14996d205 100644 --- a/src/content/docs/enterprise/team-management/teams.mdx +++ b/src/content/docs/enterprise/team-management/teams.mdx @@ -14,7 +14,7 @@ A team is a group of Warp users who collaborate together. Teams share a dedicate Teams are the foundation of Warp's enterprise experience — they enable centralized administration, shared configuration, and team-wide policy enforcement through the [Admin Panel](/enterprise/team-management/admin-panel/). :::note -Each Warp user can be an admin or member of one team at a time. +A workspace with a single team keeps a user to one team. On an Enterprise account whose workspace has multiple teams, a user can belong to more than one — see [Workspaces](/enterprise/team-management/workspaces/). ::: ## Creating a team @@ -145,8 +145,11 @@ Team Admins cannot demote or modify the Team Owner's role. The Owner role can on For detailed information on what each role can do and how settings enforcement works, see [Roles and permissions](/enterprise/team-management/roles-and-permissions/). +On an Enterprise account whose workspace holds multiple teams, a company-wide workspace admin or owner role sits above the Team Owner and Team Admin roles described here — see [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). + ## Related resources +* [Workspaces](/enterprise/team-management/workspaces/) - How workspaces, teams, and roles relate on a multi-team Enterprise account * [Admin Panel](/enterprise/team-management/admin-panel/) - Configure team settings and enforce policies * [Roles and permissions](/enterprise/team-management/roles-and-permissions/) - Detailed permission breakdowns and settings enforcement * [Getting started for admins](/enterprise/getting-started/getting-started-enterprise/) - Admin onboarding guide diff --git a/src/content/docs/enterprise/team-management/workspaces.mdx b/src/content/docs/enterprise/team-management/workspaces.mdx new file mode 100644 index 000000000..ac18b5749 --- /dev/null +++ b/src/content/docs/enterprise/team-management/workspaces.mdx @@ -0,0 +1,84 @@ +--- +title: Workspaces +description: >- + Workspaces group multiple teams under one enterprise account, with + company-wide roles, billing, and settings that sit above each team's own + configuration. +--- + +:::note +The workspace on this page is Warp's organizational layer above teams. It's unrelated to the per-team shared workspace in [Warp Drive](/knowledge-and-collaboration/warp-drive/), and to a Slack workspace, which is a separate company account you [connect through the Slack integration](/platform/integrations/slack/). +::: + +A workspace is Warp's top-level organizational unit for enterprise accounts. It groups one or more teams under a single company account, with its own roles, billing, and governance settings that apply across every team inside it. + +{/* VERIFY: confirm current plan-tier availability for native (multi-team) workspaces; billing config shows it enabled only for Warp's own internal enterprise plan as of this writing */} +Workspaces with more than one team are part of Warp's Enterprise plan. Self-serve and Business plans keep the single-team model described in [Team management](/knowledge-and-collaboration/teams/): the workspace still exists underneath, but it always contains exactly one team, so the team remains the only management surface you see. + +## Workspace vs. team + +A **team** is Warp's collaboration unit: members share a Warp Drive, cloud agent runs, environments, and secrets, and a team admin can configure team-level settings. A **workspace** is the account-level container above one or more teams. On an enterprise workspace with multiple teams: + +* Billing (the service agreement, credit pool, and spend caps) attaches to the workspace, not to any single team. +* Company-wide governance settings — like secret redaction or AI autonomy limits — are configured once at the workspace level instead of being copied across teams. +* A user is a member of the workspace first, and of zero or more teams inside it. + +## Workspace roles + +Every workspace member has one of three roles: + +* **Member** - Default role. Uses Warp within whatever teams they belong to and the settings admins configure. +* **Admin** - Manages workspace membership, billing, and settings, and has admin-level access to every team in the workspace — including teams they don't personally belong to. A workspace can have any number of admins. +* **Owner** - The workspace's single highest-privilege role. Has every admin capability, plus the ability to transfer ownership to another member. There's always exactly one owner, and they can't be removed or demoted without first transferring ownership. + +A workspace admin or owner automatically has admin-level permissions on every team in the workspace, regardless of their own membership role on that team. A team's own admin retains full control of that team, but has no authority outside it. In the team members list, a workspace-level admin or owner appears with a **Workspace admin** or **Workspace owner** badge, so members can tell a company-wide admin apart from a team-only one. + +## Teams inside a workspace + +Workspace admins create teams from the Admin Panel, giving each one a name, a color, and a visibility: + +* **Open** - Any workspace member can see the team and join it immediately. +* **Private** - Any workspace member can see the team exists. {/* VERIFY: requesting to join a Private team isn't live yet per specs/team-joining-flows; confirm current UI before publishing */} +* **Hidden** - The team doesn't appear in team discovery; an admin has to add members directly. + +Both workspace admins and a team's own admins can rename a team, change its color or visibility, and manage its members and its deletion. Only workspace admins can create a new team. A workspace member can belong to more than one team at a time. + +## Joining a workspace or team + +New members reach a workspace and its teams through a few paths: + +{/* VERIFY: confirm the workspace-level invite link and domain capture flows are live, not just specced */} +* **Invite links** - A team's invite link adds someone directly to that team, and to the workspace if they're not already in it. A workspace-level invite link additionally lets a new member pick an open team as part of accepting. +* **Email invites** - The team or workspace invite link, addressed to a specific email instead of shared as a link. +* **Domain capture** - When a workspace admin enables it for a verified company domain, anyone who signs up with a matching work email is automatically added to the workspace. +* **Team discovery** - Anyone who lands in the workspace without a team, from any of the paths above, sees a list of open teams they can join with one click under **Settings** > **Teams**. + +A user belongs to at most one workspace at a time. + +## Teamless members + +A workspace member isn't required to belong to a team. This "teamless" state is meant to be temporary — for example, right after joining the workspace and before an admin places them on a team. + +A teamless member is still a full workspace member: the workspace's plan, billing, and governance settings continue to apply to them, and workspace admins can see and manage them from the Admin Panel. {/* VERIFY: confirm the exact current scope of teamless-member restrictions (cloud agent runs, environments, secrets, scheduled agents) against shipped behavior */} What they lose access to is team-scoped collaboration and cloud agent surfaces — joining a team is required to trigger cloud agent runs or use team-owned environments and secrets. Workspace admins and owners are exempt from these restrictions, since they already have oversight access to every team's resources. + +## Workspace settings and team settings + +Settings that used to live only on the team — AI autonomy, secret redaction, sharing, codebase indexing, and similar policies in the [Admin Panel](/enterprise/team-management/admin-panel/) — now resolve across the workspace and team layers on a multi-team workspace. Each setting follows one of four patterns: + +* **Workspace-enforced** - The workspace admin sets one value that applies to every team; team admins can't override it. Billing caps, the credit pool, and domain capture always work this way. +* **Delegated ("respect team setting")** - The workspace admin can either enforce a value or leave it to each team to decide, the same way a delegated team setting can respect each user's own preference. +* **Combined** - Entries from both levels apply together. A blocked-commands list is a union — an entry from either level takes effect; an allowed-commands list is an intersection — only entries present at both levels apply. +* **Team-controlled** - The workspace layer never touches this setting. Custom model configuration and enabled agent harnesses stay team-only. + +When a workspace enforces a setting, a team admin sees it locked with an indicator that the workspace controls it — the same pattern an individual user sees today for a team-enforced setting. + +## Workspace spend limits + +On a multi-team workspace, an optional workspace-level spend cap sits above the [team-level spend limits](/enterprise/support-and-resources/billing/#monthly-spending-limits) and any per-user limits. All three levels are independent and optional, and whichever cap is hit first blocks further usage in its scope: a workspace cap blocks every team, a team cap blocks only that team, and a per-user limit blocks only that person. Workspace admins can see spend at every level; a team admin sees only their own team's usage, plus a generic notice when a workspace-level cap is the one that blocked them. + +## Related pages + +* [Team management](/knowledge-and-collaboration/teams/) - Creating and joining a team +* [Admin panel](/enterprise/team-management/admin-panel/) - Configure settings enforced across a workspace or team +* [Roles and permissions](/enterprise/team-management/roles-and-permissions/) - Team-level roles and what each can do +* [Enterprise billing](/enterprise/support-and-resources/billing/) - Credit pools, spend limits, and billing management diff --git a/src/content/docs/knowledge-and-collaboration/admin-panel.mdx b/src/content/docs/knowledge-and-collaboration/admin-panel.mdx index de74acd8f..27b068c51 100644 --- a/src/content/docs/knowledge-and-collaboration/admin-panel.mdx +++ b/src/content/docs/knowledge-and-collaboration/admin-panel.mdx @@ -15,6 +15,8 @@ The [Admin Panel](https://app.warp.dev/admin/) provides team administrators with Admin Panel access is restricted to team administrators. Right now, only the creator of a team is the designated admin. If your admin has set up styles that override user preferences, you will not be able to control them inside of Warp, and you'll see a note that your admin has configured this setting. ::: +On an Enterprise account with more than one team, many of these settings are configured once at the workspace level instead of per team — see [Workspaces](/enterprise/team-management/workspaces/#workspace-settings-and-team-settings). + **Key features:** * **AI Settings** - Control agent autonomy, permissions, and allowlists across your team diff --git a/src/content/docs/knowledge-and-collaboration/teams.mdx b/src/content/docs/knowledge-and-collaboration/teams.mdx index 9eaad2971..dd97596ee 100644 --- a/src/content/docs/knowledge-and-collaboration/teams.mdx +++ b/src/content/docs/knowledge-and-collaboration/teams.mdx @@ -5,14 +5,14 @@ description: >- --- import VideoEmbed from '@components/VideoEmbed.astro'; -A Warp team is a group of users who collaborate through a shared workspace in Warp Drive. Teams share Workflows, Notebooks, Prompts, Rules, and Environment Variables, with role-based permissions for admins and members. Each Warp user can belong to one team at a time. +A Warp team is a group of users who collaborate through a shared workspace in Warp Drive. Teams share Workflows, Notebooks, Prompts, Rules, and Environment Variables, with role-based permissions for admins and members. ## What is a team? A team is a group of Warp users who can collaborate on the command line together. Warp teams can share a dedicated workspace in Warp Drive. [Learn about pricing](https://www.warp.dev/pricing) and see our [Pricing FAQ](/support-and-community/plans-and-billing/pricing-faqs/). :::note -Currently, each Warp user can only be an admin or member of one team at a time. +On self-serve and Business plans, each Warp user can only be an admin or member of one team at a time. Enterprise accounts on the multi-team workspace model can belong to more than one team — see [Workspaces](/enterprise/team-management/workspaces/). ::: @@ -108,3 +108,5 @@ If you're a Team admin, and you choose to [delete your Warp](/support-and-commun | Delete a team | ✓ | | | Transfer admin | ✓ | | | [Manage billing](/support-and-community/plans-and-billing/pricing-faqs/#how-do-i-manage-my-billing) | ✓ | | + +Enterprise accounts on the multi-team workspace model add a company-wide admin role above these team roles — see [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). diff --git a/src/sidebar.ts b/src/sidebar.ts index 9433b3ed6..0a70cfca1 100644 --- a/src/sidebar.ts +++ b/src/sidebar.ts @@ -819,6 +819,7 @@ export const sidebarTopics: StarlightSidebarTopicsUserConfig = [ { label: 'Team management', items: [ + { slug: 'enterprise/team-management/workspaces', label: 'Workspaces' }, 'enterprise/team-management/teams', { slug: 'enterprise/team-management/admin-panel', label: 'Admin panel' }, { slug: 'enterprise/team-management/roles-and-permissions', label: 'Roles and permissions' }, From f7ec5a06d04359a764c467bfbf75a68c410dbefb Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 9 Sep 2026 16:26:14 -0700 Subject: [PATCH 2/7] Apply suggestion from @warp-for-oss[bot] Co-authored-by: warp-for-oss[bot] <277970191+warp-for-oss[bot]@users.noreply.github.com> --- src/content/docs/knowledge-and-collaboration/teams.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/knowledge-and-collaboration/teams.mdx b/src/content/docs/knowledge-and-collaboration/teams.mdx index dd97596ee..759be1f28 100644 --- a/src/content/docs/knowledge-and-collaboration/teams.mdx +++ b/src/content/docs/knowledge-and-collaboration/teams.mdx @@ -12,7 +12,7 @@ A Warp team is a group of users who collaborate through a shared workspace in Wa A team is a group of Warp users who can collaborate on the command line together. Warp teams can share a dedicated workspace in Warp Drive. [Learn about pricing](https://www.warp.dev/pricing) and see our [Pricing FAQ](/support-and-community/plans-and-billing/pricing-faqs/). :::note -On self-serve and Business plans, each Warp user can only be an admin or member of one team at a time. Enterprise accounts on the multi-team workspace model can belong to more than one team — see [Workspaces](/enterprise/team-management/workspaces/). +On self-serve and Business plans, each Warp user can only be an admin or member of one team at a time. Users on Enterprise accounts with the multi-team workspace model can belong to more than one team — see [Workspaces](/enterprise/team-management/workspaces/). ::: From 75fdc937f740eb1a5c9ebd5872ee3a66558adbcd Mon Sep 17 00:00:00 2001 From: "warp-agent-staging[bot]" <240773466+warp-agent-staging[bot]@users.noreply.github.com> Date: Wed, 9 Sep 2026 23:54:02 +0000 Subject: [PATCH 3/7] docs: address rework review findings on native workspaces page - Fix CRITICAL: scope multi-team availability claim to 'a limited set of accounts' instead of promising it to the entire Enterprise plan (workspaces.mdx:15). - Fix CRITICAL: correct the teamless-member exemption claim so it no longer implies admins/owners can trigger cloud agent runs without joining a team (workspaces.mdx:60/62). - Fix IMPORTANT: scope the Invite links bullet to Open teams and state how Private/Hidden teams actually add members, per changelog #15129. - Complete the Private team bullet's join-mechanism sentence. - Apply the Team discovery Settings-path suggestion. - Add terminology.md entries for Member, Owner, Private, Hidden, Workspace-enforced, and Team-controlled. - Trim and tighten prose across the page per editing-pass feedback. Co-Authored-By: Warp --- .agents/references/terminology.md | 12 ++++++++++++ .../enterprise/team-management/workspaces.mdx | 16 ++++++++-------- 2 files changed, 20 insertions(+), 8 deletions(-) diff --git a/.agents/references/terminology.md b/.agents/references/terminology.md index 927f4dd8a..c4448fbc2 100644 --- a/.agents/references/terminology.md +++ b/.agents/references/terminology.md @@ -148,6 +148,18 @@ For the summary of the most critical terms (core features, Automation Platform t - **workspace** — Warp's top-level organizational unit for enterprise accounts. It groups one or more teams under a single company account, with its own roles (member/admin/owner), billing, and governance settings. See [Workspaces](/enterprise/team-management/workspaces/). *Usage note:* Lowercase common noun, like "team." Distinct from two other uses of the word: the per-team shared workspace in **Warp Drive** ("teams share a dedicated workspace in Warp Drive"), and a **Slack workspace**, which is a separate company account in Slack. When the surrounding context doesn't already make clear which "workspace" is meant, say so explicitly (e.g. "your Warp workspace" or "your Slack workspace"). +- **Member** (workspace role) — The default workspace role: uses Warp within whatever teams they belong to and the settings admins configure. See [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). + +- **Owner** (workspace role) — The workspace's single highest-privilege role. Has every admin capability, plus the ability to transfer ownership to another member. Exactly one per workspace. See [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). + +- **Private** (team visibility) — A team visible to every workspace member, but joinable only when an admin adds or invites the member directly. See [Teams inside a workspace](/enterprise/team-management/workspaces/#teams-inside-a-workspace). + +- **Hidden** (team visibility) — A team that doesn't appear in team discovery; an admin has to add members directly. See [Teams inside a workspace](/enterprise/team-management/workspaces/#teams-inside-a-workspace). + +- **Workspace-enforced** (setting pattern) — A workspace setting the workspace admin sets once for every team, with no per-team override. See [Workspace settings and team settings](/enterprise/team-management/workspaces/#workspace-settings-and-team-settings). + +- **Team-controlled** (setting pattern) — A setting the workspace layer never touches; it stays team-only. See [Workspace settings and team settings](/enterprise/team-management/workspaces/#workspace-settings-and-team-settings). + ## Automation Platform terminology Renamed from "Oz" on 2026-08-18. Two surfaces keep the Oz name until 2026-10-06 diff --git a/src/content/docs/enterprise/team-management/workspaces.mdx b/src/content/docs/enterprise/team-management/workspaces.mdx index ac18b5749..7a0b9a01c 100644 --- a/src/content/docs/enterprise/team-management/workspaces.mdx +++ b/src/content/docs/enterprise/team-management/workspaces.mdx @@ -13,7 +13,7 @@ The workspace on this page is Warp's organizational layer above teams. It's unre A workspace is Warp's top-level organizational unit for enterprise accounts. It groups one or more teams under a single company account, with its own roles, billing, and governance settings that apply across every team inside it. {/* VERIFY: confirm current plan-tier availability for native (multi-team) workspaces; billing config shows it enabled only for Warp's own internal enterprise plan as of this writing */} -Workspaces with more than one team are part of Warp's Enterprise plan. Self-serve and Business plans keep the single-team model described in [Team management](/knowledge-and-collaboration/teams/): the workspace still exists underneath, but it always contains exactly one team, so the team remains the only management surface you see. +Multi-team workspaces are an Enterprise-plan capability, currently available to a limited set of accounts. Self-serve and Business plans keep the single-team model described in [Team management](/knowledge-and-collaboration/teams/): the workspace still exists underneath, but it always contains exactly one team, so the team remains the only management surface you see. ## Workspace vs. team @@ -31,14 +31,14 @@ Every workspace member has one of three roles: * **Admin** - Manages workspace membership, billing, and settings, and has admin-level access to every team in the workspace — including teams they don't personally belong to. A workspace can have any number of admins. * **Owner** - The workspace's single highest-privilege role. Has every admin capability, plus the ability to transfer ownership to another member. There's always exactly one owner, and they can't be removed or demoted without first transferring ownership. -A workspace admin or owner automatically has admin-level permissions on every team in the workspace, regardless of their own membership role on that team. A team's own admin retains full control of that team, but has no authority outside it. In the team members list, a workspace-level admin or owner appears with a **Workspace admin** or **Workspace owner** badge, so members can tell a company-wide admin apart from a team-only one. +A workspace admin or owner has admin-level permissions on every team in the workspace, even ones they don't belong to. A team's own admin retains full control of that team, but no authority outside it. In the team members list, a workspace-level admin or owner carries a **Workspace admin** or **Workspace owner** badge, so members can tell a company-wide admin apart from a team-only one. ## Teams inside a workspace Workspace admins create teams from the Admin Panel, giving each one a name, a color, and a visibility: * **Open** - Any workspace member can see the team and join it immediately. -* **Private** - Any workspace member can see the team exists. {/* VERIFY: requesting to join a Private team isn't live yet per specs/team-joining-flows; confirm current UI before publishing */} +* **Private** - Any workspace member can see the team exists, but joining requires an admin to add or invite them directly. {/* VERIFY: requesting to join a Private team isn't live yet per specs/team-joining-flows; confirm current UI before publishing */} * **Hidden** - The team doesn't appear in team discovery; an admin has to add members directly. Both workspace admins and a team's own admins can rename a team, change its color or visibility, and manage its members and its deletion. Only workspace admins can create a new team. A workspace member can belong to more than one team at a time. @@ -48,10 +48,10 @@ Both workspace admins and a team's own admins can rename a team, change its colo New members reach a workspace and its teams through a few paths: {/* VERIFY: confirm the workspace-level invite link and domain capture flows are live, not just specced */} -* **Invite links** - A team's invite link adds someone directly to that team, and to the workspace if they're not already in it. A workspace-level invite link additionally lets a new member pick an open team as part of accepting. -* **Email invites** - The team or workspace invite link, addressed to a specific email instead of shared as a link. +* **Invite links** - An Open team's invite link adds someone directly to that team, and to the workspace if they're not already in it. A workspace-level invite link additionally lets a new member pick an open team as part of accepting. Private and Hidden teams don't support invite-by-link — an admin adds those members directly. +* **Email invites** - A team or workspace invite addressed to a specific email instead of shared as a link — the way to add someone to a Private or Hidden team. * **Domain capture** - When a workspace admin enables it for a verified company domain, anyone who signs up with a matching work email is automatically added to the workspace. -* **Team discovery** - Anyone who lands in the workspace without a team, from any of the paths above, sees a list of open teams they can join with one click under **Settings** > **Teams**. +* **Team discovery** - Anyone who lands in the workspace without a team, from any of the paths above, sees a list of open teams they can join with one click in the Warp app under **Settings** > **Teams**. A user belongs to at most one workspace at a time. @@ -59,7 +59,7 @@ A user belongs to at most one workspace at a time. A workspace member isn't required to belong to a team. This "teamless" state is meant to be temporary — for example, right after joining the workspace and before an admin places them on a team. -A teamless member is still a full workspace member: the workspace's plan, billing, and governance settings continue to apply to them, and workspace admins can see and manage them from the Admin Panel. {/* VERIFY: confirm the exact current scope of teamless-member restrictions (cloud agent runs, environments, secrets, scheduled agents) against shipped behavior */} What they lose access to is team-scoped collaboration and cloud agent surfaces — joining a team is required to trigger cloud agent runs or use team-owned environments and secrets. Workspace admins and owners are exempt from these restrictions, since they already have oversight access to every team's resources. +A teamless member is still a full workspace member: the workspace's plan, billing, and governance settings continue to apply to them, and workspace admins can see and manage them from the Admin Panel. {/* VERIFY: confirm the exact current scope of teamless-member restrictions (cloud agent runs, environments, secrets, scheduled agents) against shipped behavior */} What they lose access to is team-scoped collaboration: joining a team is required to trigger cloud agent runs or use team-owned environments and secrets — this applies to workspace admins and owners as well, even though they can already view and manage every team's resources from the Admin Panel. ## Workspace settings and team settings @@ -70,7 +70,7 @@ Settings that used to live only on the team — AI autonomy, secret redaction, s * **Combined** - Entries from both levels apply together. A blocked-commands list is a union — an entry from either level takes effect; an allowed-commands list is an intersection — only entries present at both levels apply. * **Team-controlled** - The workspace layer never touches this setting. Custom model configuration and enabled agent harnesses stay team-only. -When a workspace enforces a setting, a team admin sees it locked with an indicator that the workspace controls it — the same pattern an individual user sees today for a team-enforced setting. +When a workspace enforces a setting, team admins see it locked with an indicator that the workspace controls it. ## Workspace spend limits From c1afce9d0d527e18eccc7a7ec021e0bee3b5e994 Mon Sep 17 00:00:00 2001 From: "warp-agent-staging[bot]" <240773466+warp-agent-staging[bot]@users.noreply.github.com> Date: Thu, 10 Sep 2026 00:23:41 +0000 Subject: [PATCH 4/7] docs: correct the native workspaces role model and mark unverified claims Scope the Team Owner role and ownership transfer to the single-team model, state that ownership is workspace-level on a multi-team workspace, mark the cross-team admin authority claim with a VERIFY marker, and complete the workspace glossary. Co-Authored-By: Warp --- .agents/references/terminology.md | 6 ++++++ .../enterprise/team-management/roles-and-permissions.mdx | 2 +- src/content/docs/enterprise/team-management/teams.mdx | 2 +- .../docs/enterprise/team-management/workspaces.mdx | 8 ++++++-- 4 files changed, 14 insertions(+), 4 deletions(-) diff --git a/.agents/references/terminology.md b/.agents/references/terminology.md index c4448fbc2..eb45bdaec 100644 --- a/.agents/references/terminology.md +++ b/.agents/references/terminology.md @@ -150,6 +150,8 @@ For the summary of the most critical terms (core features, Automation Platform t - **Member** (workspace role) — The default workspace role: uses Warp within whatever teams they belong to and the settings admins configure. See [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). +- **Admin** (workspace role) — Manages workspace membership, billing, and settings, and has admin-level access to the teams in the workspace. A workspace can have any number of admins. See [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). + - **Owner** (workspace role) — The workspace's single highest-privilege role. Has every admin capability, plus the ability to transfer ownership to another member. Exactly one per workspace. See [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). - **Private** (team visibility) — A team visible to every workspace member, but joinable only when an admin adds or invites the member directly. See [Teams inside a workspace](/enterprise/team-management/workspaces/#teams-inside-a-workspace). @@ -158,6 +160,10 @@ For the summary of the most critical terms (core features, Automation Platform t - **Workspace-enforced** (setting pattern) — A workspace setting the workspace admin sets once for every team, with no per-team override. See [Workspace settings and team settings](/enterprise/team-management/workspaces/#workspace-settings-and-team-settings). +- **Delegated** (setting pattern) — A setting the workspace admin can either enforce or leave to each team to decide. Also written "respect team setting." See [Workspace settings and team settings](/enterprise/team-management/workspaces/#workspace-settings-and-team-settings). + +- **Combined** (setting pattern) — A setting where entries from the workspace and team levels apply together: a blocked list is a union, an allowed list an intersection. See [Workspace settings and team settings](/enterprise/team-management/workspaces/#workspace-settings-and-team-settings). + - **Team-controlled** (setting pattern) — A setting the workspace layer never touches; it stays team-only. See [Workspace settings and team settings](/enterprise/team-management/workspaces/#workspace-settings-and-team-settings). ## Automation Platform terminology diff --git a/src/content/docs/enterprise/team-management/roles-and-permissions.mdx b/src/content/docs/enterprise/team-management/roles-and-permissions.mdx index 9ee2dc656..b53204d8f 100644 --- a/src/content/docs/enterprise/team-management/roles-and-permissions.mdx +++ b/src/content/docs/enterprise/team-management/roles-and-permissions.mdx @@ -8,7 +8,7 @@ description: >- Warp uses a role-based access model to control what team members can do within your organization. Admins manage team settings and enforce policies, while members use Warp's features within the boundaries admins define. :::note -On an Enterprise account whose workspace holds multiple teams, a company-wide workspace role (member, admin, or owner) sits above the team roles described here — see [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). +The roles on this page describe a workspace with a single team. On an Enterprise account whose workspace holds multiple teams, a company-wide workspace role (member, admin, or owner) sits above the team layer and ownership belongs to the workspace rather than to any one team — see [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). ::: ## User roles diff --git a/src/content/docs/enterprise/team-management/teams.mdx b/src/content/docs/enterprise/team-management/teams.mdx index 14996d205..13d09b904 100644 --- a/src/content/docs/enterprise/team-management/teams.mdx +++ b/src/content/docs/enterprise/team-management/teams.mdx @@ -145,7 +145,7 @@ Team Admins cannot demote or modify the Team Owner's role. The Owner role can on For detailed information on what each role can do and how settings enforcement works, see [Roles and permissions](/enterprise/team-management/roles-and-permissions/). -On an Enterprise account whose workspace holds multiple teams, a company-wide workspace admin or owner role sits above the Team Owner and Team Admin roles described here — see [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). +The Team Owner role and the ownership transfer described above apply to a workspace with a single team. On an Enterprise account whose workspace holds multiple teams, ownership sits at the workspace level instead, and a company-wide workspace admin or owner sits above each team's own admins — see [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). ## Related resources diff --git a/src/content/docs/enterprise/team-management/workspaces.mdx b/src/content/docs/enterprise/team-management/workspaces.mdx index 7a0b9a01c..4da0f8a1f 100644 --- a/src/content/docs/enterprise/team-management/workspaces.mdx +++ b/src/content/docs/enterprise/team-management/workspaces.mdx @@ -28,9 +28,10 @@ A **team** is Warp's collaboration unit: members share a Warp Drive, cloud agent Every workspace member has one of three roles: * **Member** - Default role. Uses Warp within whatever teams they belong to and the settings admins configure. -* **Admin** - Manages workspace membership, billing, and settings, and has admin-level access to every team in the workspace — including teams they don't personally belong to. A workspace can have any number of admins. +* **Admin** - Manages workspace membership, billing, and settings, and has admin-level access to the teams in the workspace. A workspace can have any number of admins. * **Owner** - The workspace's single highest-privilege role. Has every admin capability, plus the ability to transfer ownership to another member. There's always exactly one owner, and they can't be removed or demoted without first transferring ownership. +{/* VERIFY: confirm a workspace admin's admin-level permissions extend to teams they don't belong to in the shipped client; specs/workspace-admin-roles invariants 18-19 define it, but changelog #15123 confirms only membership management on the admin's own team */} A workspace admin or owner has admin-level permissions on every team in the workspace, even ones they don't belong to. A team's own admin retains full control of that team, but no authority outside it. In the team members list, a workspace-level admin or owner carries a **Workspace admin** or **Workspace owner** badge, so members can tell a company-wide admin apart from a team-only one. ## Teams inside a workspace @@ -43,6 +44,9 @@ Workspace admins create teams from the Admin Panel, giving each one a name, a co Both workspace admins and a team's own admins can rename a team, change its color or visibility, and manage its members and its deletion. Only workspace admins can create a new team. A workspace member can belong to more than one team at a time. +{/* VERIFY: confirm the team Owner role stays hidden on multi-team workspaces in the shipped client; specs/team-crud deprecates it in favor of workspace-level ownership and drops the Owner chip and transfer-ownership action, but no public changelog entry confirms it */} +A team itself has two roles, member and admin. Ownership belongs to the workspace rather than to any one team, so the [Team Owner role](/enterprise/team-management/teams/#team-roles-and-permissions) of the single-team model doesn't apply here. + ## Joining a workspace or team New members reach a workspace and its teams through a few paths: @@ -59,7 +63,7 @@ A user belongs to at most one workspace at a time. A workspace member isn't required to belong to a team. This "teamless" state is meant to be temporary — for example, right after joining the workspace and before an admin places them on a team. -A teamless member is still a full workspace member: the workspace's plan, billing, and governance settings continue to apply to them, and workspace admins can see and manage them from the Admin Panel. {/* VERIFY: confirm the exact current scope of teamless-member restrictions (cloud agent runs, environments, secrets, scheduled agents) against shipped behavior */} What they lose access to is team-scoped collaboration: joining a team is required to trigger cloud agent runs or use team-owned environments and secrets — this applies to workspace admins and owners as well, even though they can already view and manage every team's resources from the Admin Panel. +A teamless member is still a full workspace member: the workspace's plan, billing, and governance settings continue to apply to them, and workspace admins can see and manage them from the Admin Panel. {/* VERIFY: confirm the exact current scope of teamless-member restrictions (cloud agent runs, environments, secrets, scheduled agents) against shipped behavior */} What they lose access to is team-scoped collaboration: joining a team is required to trigger cloud agent runs or use team-owned environments and secrets — this applies to workspace admins and owners as well, even though they keep their workspace-level oversight in the Admin Panel. ## Workspace settings and team settings From 86ec119c0deeb7ed4a1976a7342cf01cc51393b9 Mon Sep 17 00:00:00 2001 From: "warp-agent-staging[bot]" <240773466+warp-agent-staging[bot]@users.noreply.github.com> Date: Thu, 10 Sep 2026 00:36:42 +0000 Subject: [PATCH 5/7] docs: address follow-up review findings on the workspaces page Narrow the workspace Admin bullet to workspace-scoped duties, scope team creation and the permissions table to the single-team model, lead the page with its summary, break the spend-limit rules into bullets, and complete the glossary and Admin Panel casing. Co-Authored-By: Warp --- .agents/references/terminology.md | 4 +++- .../docs/enterprise/team-management/teams.mdx | 4 ++++ .../enterprise/team-management/workspaces.mdx | 19 ++++++++++++------- 3 files changed, 19 insertions(+), 8 deletions(-) diff --git a/.agents/references/terminology.md b/.agents/references/terminology.md index eb45bdaec..b7af2ae41 100644 --- a/.agents/references/terminology.md +++ b/.agents/references/terminology.md @@ -150,10 +150,12 @@ For the summary of the most critical terms (core features, Automation Platform t - **Member** (workspace role) — The default workspace role: uses Warp within whatever teams they belong to and the settings admins configure. See [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). -- **Admin** (workspace role) — Manages workspace membership, billing, and settings, and has admin-level access to the teams in the workspace. A workspace can have any number of admins. See [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). +- **Admin** (workspace role) — Manages workspace membership, billing, and settings. A workspace can have any number of admins. See [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). - **Owner** (workspace role) — The workspace's single highest-privilege role. Has every admin capability, plus the ability to transfer ownership to another member. Exactly one per workspace. See [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). +- **Open** (team visibility) — A team any workspace member can see and join immediately. See [Teams inside a workspace](/enterprise/team-management/workspaces/#teams-inside-a-workspace). + - **Private** (team visibility) — A team visible to every workspace member, but joinable only when an admin adds or invites the member directly. See [Teams inside a workspace](/enterprise/team-management/workspaces/#teams-inside-a-workspace). - **Hidden** (team visibility) — A team that doesn't appear in team discovery; an admin has to add members directly. See [Teams inside a workspace](/enterprise/team-management/workspaces/#teams-inside-a-workspace). diff --git a/src/content/docs/enterprise/team-management/teams.mdx b/src/content/docs/enterprise/team-management/teams.mdx index 13d09b904..d7d36969c 100644 --- a/src/content/docs/enterprise/team-management/teams.mdx +++ b/src/content/docs/enterprise/team-management/teams.mdx @@ -26,6 +26,8 @@ You can create a new team in two ways: When creating a team, give it a meaningful name that represents your organization, company, or project. The person who creates the team becomes the **Team Owner**. +On an Enterprise account whose workspace holds multiple teams, team creation works differently: a workspace admin creates teams from the Admin Panel, and ownership stays at the workspace level — see [Teams inside a workspace](/enterprise/team-management/workspaces/#teams-inside-a-workspace). + :::note You can rename your team at any time by going to **Settings** > **Teams**, clicking on the team name, entering the new name, and pressing `Enter`. ::: @@ -115,6 +117,8 @@ We recommend having at least one Team Admin in addition to the Team Owner to pre ### Permissions overview +This table covers a workspace with a single team. On a multi-team workspace, only a workspace admin creates teams and there is no team Owner column — see [Workspace roles](/enterprise/team-management/workspaces/#workspace-roles). + | Action | Owner | Admin | Member | | --- | --- | --- | --- | | Create a team | ✓ | ✓ | ✓ | diff --git a/src/content/docs/enterprise/team-management/workspaces.mdx b/src/content/docs/enterprise/team-management/workspaces.mdx index 4da0f8a1f..9408160ba 100644 --- a/src/content/docs/enterprise/team-management/workspaces.mdx +++ b/src/content/docs/enterprise/team-management/workspaces.mdx @@ -6,15 +6,15 @@ description: >- configuration. --- -:::note -The workspace on this page is Warp's organizational layer above teams. It's unrelated to the per-team shared workspace in [Warp Drive](/knowledge-and-collaboration/warp-drive/), and to a Slack workspace, which is a separate company account you [connect through the Slack integration](/platform/integrations/slack/). -::: - A workspace is Warp's top-level organizational unit for enterprise accounts. It groups one or more teams under a single company account, with its own roles, billing, and governance settings that apply across every team inside it. {/* VERIFY: confirm current plan-tier availability for native (multi-team) workspaces; billing config shows it enabled only for Warp's own internal enterprise plan as of this writing */} Multi-team workspaces are an Enterprise-plan capability, currently available to a limited set of accounts. Self-serve and Business plans keep the single-team model described in [Team management](/knowledge-and-collaboration/teams/): the workspace still exists underneath, but it always contains exactly one team, so the team remains the only management surface you see. +:::note +The workspace on this page is Warp's organizational layer above teams. It's unrelated to the per-team shared workspace in [Warp Drive](/knowledge-and-collaboration/warp-drive/), and to a Slack workspace, which is a separate company account you [connect through the Slack integration](/platform/integrations/slack/). +::: + ## Workspace vs. team A **team** is Warp's collaboration unit: members share a Warp Drive, cloud agent runs, environments, and secrets, and a team admin can configure team-level settings. A **workspace** is the account-level container above one or more teams. On an enterprise workspace with multiple teams: @@ -28,7 +28,7 @@ A **team** is Warp's collaboration unit: members share a Warp Drive, cloud agent Every workspace member has one of three roles: * **Member** - Default role. Uses Warp within whatever teams they belong to and the settings admins configure. -* **Admin** - Manages workspace membership, billing, and settings, and has admin-level access to the teams in the workspace. A workspace can have any number of admins. +* **Admin** - Manages workspace membership, billing, and settings. A workspace can have any number of admins. * **Owner** - The workspace's single highest-privilege role. Has every admin capability, plus the ability to transfer ownership to another member. There's always exactly one owner, and they can't be removed or demoted without first transferring ownership. {/* VERIFY: confirm a workspace admin's admin-level permissions extend to teams they don't belong to in the shipped client; specs/workspace-admin-roles invariants 18-19 define it, but changelog #15123 confirms only membership management on the admin's own team */} @@ -78,11 +78,16 @@ When a workspace enforces a setting, team admins see it locked with an indicator ## Workspace spend limits -On a multi-team workspace, an optional workspace-level spend cap sits above the [team-level spend limits](/enterprise/support-and-resources/billing/#monthly-spending-limits) and any per-user limits. All three levels are independent and optional, and whichever cap is hit first blocks further usage in its scope: a workspace cap blocks every team, a team cap blocks only that team, and a per-user limit blocks only that person. Workspace admins can see spend at every level; a team admin sees only their own team's usage, plus a generic notice when a workspace-level cap is the one that blocked them. +On a multi-team workspace, an optional workspace-level spend cap sits above the [team-level spend limits](/enterprise/support-and-resources/billing/#monthly-spending-limits) and any per-user limits. All three levels are independent and optional, and whichever cap is hit first blocks further usage in its scope: + +* **Workspace cap** - Blocks every team in the workspace. +* **Team cap** - Blocks only that team. +* **Per-user limit** - Blocks only that person. +* **Spend visibility** - Workspace admins see spend at every level. A team admin sees only their own team's usage, plus a generic notice when a workspace-level cap is the one that blocked them. ## Related pages * [Team management](/knowledge-and-collaboration/teams/) - Creating and joining a team -* [Admin panel](/enterprise/team-management/admin-panel/) - Configure settings enforced across a workspace or team +* [Admin Panel](/enterprise/team-management/admin-panel/) - Configure settings enforced across a workspace or team * [Roles and permissions](/enterprise/team-management/roles-and-permissions/) - Team-level roles and what each can do * [Enterprise billing](/enterprise/support-and-resources/billing/) - Credit pools, spend limits, and billing management From 75aff261ced6b54a78e64e350cbee880a209a099 Mon Sep 17 00:00:00 2001 From: "warp-agent-staging[bot]" <240773466+warp-agent-staging[bot]@users.noreply.github.com> Date: Thu, 10 Sep 2026 00:56:15 +0000 Subject: [PATCH 6/7] docs: mark the remaining spec-only workspace claims for verification Add VERIFY markers for the one-workspace-per-user constraint, the four setting-resolution patterns, and the spend-cap precedence and visibility rules, each listed under Unverified claims in the PR body. Co-Authored-By: Warp --- src/content/docs/enterprise/team-management/workspaces.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/content/docs/enterprise/team-management/workspaces.mdx b/src/content/docs/enterprise/team-management/workspaces.mdx index 9408160ba..e76ececf0 100644 --- a/src/content/docs/enterprise/team-management/workspaces.mdx +++ b/src/content/docs/enterprise/team-management/workspaces.mdx @@ -57,6 +57,7 @@ New members reach a workspace and its teams through a few paths: * **Domain capture** - When a workspace admin enables it for a verified company domain, anyone who signs up with a matching work email is automatically added to the workspace. * **Team discovery** - Anyone who lands in the workspace without a team, from any of the paths above, sees a list of open teams they can join with one click in the Warp app under **Settings** > **Teams**. +{/* VERIFY: confirm a user can belong to only one workspace at a time in shipped behavior; specs/team-joining-flows treats it as an invariant, but no public source states it */} A user belongs to at most one workspace at a time. ## Teamless members @@ -69,6 +70,7 @@ A teamless member is still a full workspace member: the workspace's plan, billin Settings that used to live only on the team — AI autonomy, secret redaction, sharing, codebase indexing, and similar policies in the [Admin Panel](/enterprise/team-management/admin-panel/) — now resolve across the workspace and team layers on a multi-team workspace. Each setting follows one of four patterns: +{/* VERIFY: confirm the four setting-resolution patterns and the examples assigned to each against shipped behavior; sourced from specs/multi-team-workspace-settings, with no public source */} * **Workspace-enforced** - The workspace admin sets one value that applies to every team; team admins can't override it. Billing caps, the credit pool, and domain capture always work this way. * **Delegated ("respect team setting")** - The workspace admin can either enforce a value or leave it to each team to decide, the same way a delegated team setting can respect each user's own preference. * **Combined** - Entries from both levels apply together. A blocked-commands list is a union — an entry from either level takes effect; an allowed-commands list is an intersection — only entries present at both levels apply. @@ -80,6 +82,7 @@ When a workspace enforces a setting, team admins see it locked with an indicator On a multi-team workspace, an optional workspace-level spend cap sits above the [team-level spend limits](/enterprise/support-and-resources/billing/#monthly-spending-limits) and any per-user limits. All three levels are independent and optional, and whichever cap is hit first blocks further usage in its scope: +{/* VERIFY: confirm cap precedence and the per-role spend visibility rules, including the generic blocked-by-workspace-cap notice, against shipped behavior; sourced from specs/workspace-spend-limits */} * **Workspace cap** - Blocks every team in the workspace. * **Team cap** - Blocks only that team. * **Per-user limit** - Blocks only that person. From 85fe20fdc3af818a0805b80ac96236d00882df17 Mon Sep 17 00:00:00 2001 From: "warp-agent-staging[bot]" <240773466+warp-agent-staging[bot]@users.noreply.github.com> Date: Thu, 10 Sep 2026 01:04:44 +0000 Subject: [PATCH 7/7] docs: remove workspace disambiguation note on reviewer request Removes the ':::note' callout distinguishing the account-level workspace from the per-team Warp Drive workspace and Slack workspace, per reviewer feedback on PR #723. --- src/content/docs/enterprise/team-management/workspaces.mdx | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/content/docs/enterprise/team-management/workspaces.mdx b/src/content/docs/enterprise/team-management/workspaces.mdx index e76ececf0..9d49ba855 100644 --- a/src/content/docs/enterprise/team-management/workspaces.mdx +++ b/src/content/docs/enterprise/team-management/workspaces.mdx @@ -11,10 +11,6 @@ A workspace is Warp's top-level organizational unit for enterprise accounts. It {/* VERIFY: confirm current plan-tier availability for native (multi-team) workspaces; billing config shows it enabled only for Warp's own internal enterprise plan as of this writing */} Multi-team workspaces are an Enterprise-plan capability, currently available to a limited set of accounts. Self-serve and Business plans keep the single-team model described in [Team management](/knowledge-and-collaboration/teams/): the workspace still exists underneath, but it always contains exactly one team, so the team remains the only management surface you see. -:::note -The workspace on this page is Warp's organizational layer above teams. It's unrelated to the per-team shared workspace in [Warp Drive](/knowledge-and-collaboration/warp-drive/), and to a Slack workspace, which is a separate company account you [connect through the Slack integration](/platform/integrations/slack/). -::: - ## Workspace vs. team A **team** is Warp's collaboration unit: members share a Warp Drive, cloud agent runs, environments, and secrets, and a team admin can configure team-level settings. A **workspace** is the account-level container above one or more teams. On an enterprise workspace with multiple teams: