Workspaces

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.

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: 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. 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 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, but joining requires an admin to add or invite them directly.
• 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.

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 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:

• 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 in the Warp app 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. 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

Settings that used to live only on the team — AI autonomy, secret redaction, sharing, codebase indexing, and similar policies in the 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, team admins see it locked with an indicator that the workspace controls it.

Workspace spend limits

On a multi-team workspace, an optional workspace-level spend cap sits above the team-level spend 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 - Creating and joining a team
• Admin Panel - Configure settings enforced across a workspace or team
• Roles and permissions - Team-level roles and what each can do
• Enterprise billing - Credit pools, spend limits, and billing management