How do I set up Windsurf Teams ($30/user/mo) with centralized billing, admin analytics, and automated zero data retention?

Most teams hit the same wall when they scale AI coding: individual devs love the speed, finance wants one invoice, security wants proofs of data handling, and eng leaders want a clear picture of how the tooling is actually used. Windsurf Teams is built to line those up: centralized billing, admin analytics, and automated zero data retention so you can move fast without losing governance.

Quick Answer: Windsurf Teams is a cloud plan for engineering orgs that want multi-seat access to the Windsurf Editor with central billing, built‑in admin analytics, and zero‑data‑retention defaults for all AI traffic—no extra configuration required.

The Quick Overview

What It Is: A Windsurf plan for groups of developers that layers organization controls—centralized billing, analytics, and strict data retention policies—on top of the core Windsurf editor, Cascade, Tab, and integrations.
Who It Is For: Eng orgs, platform teams, and security-conscious startups that need governance and predictability around AI coding tools, not just individual subscriptions.
Core Problem Solved: You replace a sprawl of one-off subscriptions and unknown data flows with a single, governed workspace that’s easy to buy, easy to audit, and safe to scale.

How It Works

At a high level, Windsurf Teams gives you an organization layer on top of the standard Windsurf experience. You create a team, invite developers, and everything they do with Windsurf’s AI—Cascade conversations, Tab usage, browser calls—runs under that team’s policies and billing.

Under the hood:

Organization Setup & Billing:
You register or upgrade to a Teams plan, configure billing once for the whole org, and assign seats. Devs join via invite so their usage routes to the team account and invoice.
Admin Analytics & Governance:
As an admin, you get an analytics dashboard to track adoption and usage, and manage access. You can see how the team is using Windsurf without inspecting private code or prompts.
Automated Zero Data Retention:
On Teams (and Enterprise) plans, Windsurf enforces zero‑data retention by default for AI inputs and outputs. Requests are routed through Windsurf’s managed infrastructure, but prompts and completions are not stored to train models, giving you a compliant baseline without custom setup.

Step‑by‑Step: Setting Up Windsurf Teams

1. Create or Upgrade to a Teams Workspace

Sign in to your Windsurf account at windsurf.ai.
Go to your Account or Billing area (usually via your avatar menu).
Choose Upgrade or Create a Team.
Select Teams as your plan.

Note: Official documentation now lists Teams at $40 per user/month. If you previously saw $30/user/mo, that was an older price; the setup flow is the same.

Enter your organization name (e.g., Acme Engineering).
Add billing details (company card, billing contact email, and any required tax info).
Confirm seat count for your initial rollout—you can grow this later.

Once you confirm, your account becomes a team workspace and all org‑level features (billing, analytics, ZDR) apply to that workspace.

2. Configure Centralized Billing

Centralized billing means your finance team gets one predictable bill instead of 20 scattered expense reports.

In your new team workspace, open Settings → Billing.
Verify:
- Plan: Teams
- Seats: Matches the number of developers you’re onboarding
- Billing cadence: Monthly (or annual, if offered in your contract)
Add:
- Billing contact: Typically a finance or ops distribution email.
- Company information: Legal name, address, and any PO or internal reference IDs.
Save changes. From now on:
- All invited users’ usage under this workspace flows to this single invoice.
- Individual Pro/Free accounts your devs use outside this workspace remain separate.

If you’re migrating devs from individual Pro to Teams, have them:

Join the new Teams workspace, and
Use Windsurf in the context of that workspace so usage is billed centrally.

3. Invite Developers and Assign Seats

Go to Settings → Members (or similar “Team members” page).
Click Invite members.
Enter work emails for your developers (ideally your SSO/HRIS canonical emails).
Assign roles:
- Admin: For platform/DevEx leads who manage seats and analytics.
- Member: For most developers.
Send invites.

Each developer will:

Accept the invite via email.
Log into Windsurf.
Connect their editor (Windsurf Editor or JetBrains plugin) to the Teams workspace.

Now, everything they do with Cascade, Tab, Browser, Previews, and terminal assistance under that workspace is covered by your Teams policies and billing.

4. Use the Admin Dashboard & Analytics

Once the team is active, the admin dashboard becomes your observability layer for AI adoption.

In Settings → Admin Dashboard / Analytics, you’ll typically see:

Seat utilization: How many of your purchased seats are actually in use.
Active users: Which devs are regularly using Windsurf.
Usage metrics: Aggregated information about how often Windsurf is invoked (e.g., Cascade sessions, Tab usage), without exposing individual prompt contents.

This lets you:

Justify spend to leadership with concrete adoption data.
Spot unused seats to reassign or reclaim.
Identify teams that might need training or onboarding support.

5. Understand Automated Zero Data Retention (ZDR)

On Teams (and Enterprise) plans, Windsurf enforces automated zero data retention for AI traffic by default:

Scope: All AI requests (e.g., Cascade conversations, Tab completions, browser-augmented calls) from your team workspace.
What it means technically:
- Inputs and outputs to AI providers are processed and routed on servers managed by Windsurf or subprocessors.
- For Teams and Enterprise, those inputs/outputs are not retained for training or long‑term storage by Windsurf or its model providers.
- The system is configured to avoid keeping AI content beyond what’s needed to fulfill the request and maintain immediate context.

You do not need to toggle a setting to “turn on” ZDR—Teams plans ship with this as the default posture.

If your security team asks:

“Where is our code going?” → AI requests are handled in Windsurf’s managed cloud infrastructure and subprocessors, but subject to zero‑data retention for your plan.
“Is our data used to train models?” → Under Teams and Enterprise, prompts and completions are not stored for training; they follow ZDR defaults.
“Can we get a different deployment mode?” → That’s where Enterprise + Hybrid / Self‑hosted come in (more below).

Features & Benefits Breakdown

Core Feature	What It Does	Primary Benefit
Centralized Billing	Routes all team usage under one organization invoice and billing profile.	Predictable spend; fewer individual reimbursements and audits.
Admin Dashboard & Analytics	Gives admins a view into seat usage and high‑level adoption.	Data‑driven license management and rollout planning.
Automated Zero Data Retention	Enforces zero‑data retention for AI inputs/outputs by default on Teams and Enterprise plans.	Satisfies strict data‑handling policies with minimal setup.

Ideal Use Cases

Best for mid‑size eng orgs formalizing AI tools:
Because it gives you centralized billing and analytics, so you can stop wrangling individual subscriptions and start treating AI coding as shared infra.
Best for regulated or security‑sensitive teams not yet ready for Hybrid/Self‑hosted:
Because automated zero data retention on Teams provides a strong default data posture without taking on infrastructure overhead.

Limitations & Considerations

ZDR is a cloud policy, not a private deployment:
Automated zero data retention means prompts and completions aren’t stored for training, but your compute still runs in Windsurf’s cloud. If your policy mandates no code ever leaves your network, you’ll want to evaluate Enterprise Hybrid or Self‑hosted.
SSO, RBAC, and advanced access controls are Enterprise features:
Teams gets centralized billing, analytics, and ZDR by default. If you need SSO, granular RBAC, or Hybrid deployment, those live under the Enterprise plan.

Pricing & Plans

Windsurf offers multiple plans; Teams sits between individual and full Enterprise:

Free / Pro / Max: For individual developers and power users who want the full AI experience but don’t need org‑level controls.
Teams – $40/user/month: For groups that need centralized billing, admin analytics, and automated zero data retention—ideal for the first formal rollout across a company or business unit.
Enterprise – Custom pricing: For organizations that need everything in Teams plus:
- RBAC and advanced access controls
- SSO and enterprise authentication
- Hybrid deployment option and additional governance controls
- Highest‑priority support and dedicated account management
Teams: Best for engineering orgs that want to standardize on Windsurf, with predictable costs, visibility, and ZDR, but are okay with cloud deployment.
Enterprise: Best for larger or regulated organizations that need SSO, RBAC, Hybrid or Self‑hosted deployment, and formal procurement and security reviews.

Frequently Asked Questions

Do I need to turn on zero data retention for my Windsurf Teams workspace?

Short Answer: No. Automated zero data retention is enabled by default for Teams and Enterprise workspaces.

Details:
On Teams and Enterprise plans, Windsurf configures AI routing so that inputs and outputs follow zero‑data retention policies automatically. That means prompts and completions are processed to fulfill requests but are not stored to train models. You don’t have to flip a switch, add a header, or maintain a custom allowlist—just ensure your developers are actually using the Teams workspace (not personal accounts) for work that requires ZDR.

What if we outgrow Teams and need SSO or Hybrid deployment?

Short Answer: You can upgrade from Teams to Enterprise to add SSO, RBAC, and Hybrid deployment.

Details:
Teams is designed as the on‑ramp: you get centralized billing, analytics, and ZDR for multi‑seat usage. If your organization later requires:

Integration with SSO (Okta, Azure AD, etc.),
Granular RBAC (e.g., per‑group access rules),
Hybrid deployment (e.g., Docker Compose + Cloudflare Tunnel) or fully Self‑hosted options,

you can work with Windsurf’s sales and solutions team to upgrade to Enterprise. Your existing team structure and users can be preserved; the upgrade primarily unlocks additional controls, deployment options, and support levels.

Summary

Setting up Windsurf Teams is straightforward: create a team workspace, configure centralized billing once, invite your developers, and start tracking adoption via the admin dashboard. Under the hood, your AI traffic inherits automated zero data retention by default, giving security and compliance a strong starting point without turning your rollout into a months‑long infrastructure project.

As someone who’s rolled out internal tools across thousands of engineers, my recommendation is simple: start with a small Teams cohort, confirm the value and ZDR posture with your security stakeholders, then scale seats once you see the flow-state gains—multi-file edits, lint‑clean code, and PRs shipping faster—across the org.

Next Step

Get Started