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 the moment AI coding goes from “cool demo” to “real rollout”: who’s paying, who’s in, who’s out, what’s logged, and what (if anything) is kept. Windsurf Teams is built to answer exactly that—centralized billing, admin analytics, and automated zero data retention—without yanking developers out of flow.

Quick Answer: Windsurf Teams is a managed, cloud-based plan designed for engineering orgs that want AI superpowers in the IDE plus centralized billing, visibility, and automated zero data retention for all AI interactions by default.

The Quick Overview

What It Is: Windsurf Teams is a team-tier plan that layers admin controls, analytics, and compliance-friendly defaults on top of the core Windsurf experience.
Who It Is For: Engineering leaders, platform teams, and security-conscious orgs that want to standardize on Windsurf across a group of developers.
Core Problem Solved: It eliminates shadow AI tools and one-off subscriptions by giving you a single place to manage seats, understand usage, and enforce data-handling expectations—while keeping developers in the same agentic IDE they already love.

How It Works

At a high level, setting up Windsurf Teams follows a simple flow: create an org-level workspace, add billing, invite your developers, and let Windsurf’s cloud handle all AI compute with automated zero data retention for your team’s requests.

Behind the scenes, your developers keep working inside the Windsurf Editor (or via plugins), with Cascade and Tab powered from Windsurf’s cloud. On any Teams or Enterprise plan, all inputs and outputs to AI requests follow zero-data retention policies by default—no prompts, code, or model outputs are stored in the underlying model providers’ logs.

Here’s how the setup typically breaks down:

Create and Configure Your Team Workspace:
Set up a Team in Windsurf, assign an owner/admin, and connect centralized billing for all seats.
Invite Members and Roll Out Access:
Add developers by email or domain, map them to the correct plan, and standardize how they authenticate into Windsurf (e.g., shared invite links or SSO via Enterprise when you’re ready for that step).
Monitor Usage via Admin Analytics:
Use the admin dashboard to track adoption, usage patterns, and value—while automated zero data retention keeps prompts and outputs protected by design.

Step 1: Create Your Windsurf Teams Workspace

First, you’ll create a shared “home” for your org in Windsurf.

Sign in with your primary admin account
- Use the email you want tied to billing and admin ownership (often a shared ops or platform address).
- If you’re already on an individual Free/Pro plan, this account can be upgraded to Teams.
Navigate to Teams setup
- From the Windsurf web dashboard (windsurf.ai) or the account menu in the app, go to Settings or Billing.
- Look for a Teams or Create Team entry point.
Name your Team
- Choose an org-meaningful name (e.g., Acme Engineering, Acme Platform, Acme AI Guild).
- This name will show up in admin dashboards and (for users) in context where they select which org they belong to, if they have multiple.
Confirm the Teams plan
- Select the Teams plan tier.
- Pricing is per user / per month, billed centrally to the Team owner. (If your UI still shows the legacy $30 number from the question, note that Windsurf’s current docs list Teams at $40/user/month; always rely on the price shown in-product at checkout.)

Once this is saved, you’ve got a dedicated Team workspace—separate from any individual usage.

Step 2: Set Up Centralized Billing

Centralized billing is what turns “a bunch of devs trying Windsurf” into “a managed, budgetable tool.”

Add your payment method
- In the Team workspace, open Billing or Plans & Billing.
- Add a corporate credit card or payment method.
- Confirm currency and billing cadence (monthly vs annual, if offered).
Choose seat count and assignment strategy
- Decide if you’ll:
  - Start small with a core group (e.g., platform team or pilot squad).
  - Or roll out broadly and trim later based on analytics.
- Many teams start with 10–50 seats, then expand as usage proves out.
Understand how charges map to users
- Teams is billed per active user / month associated with your Team.
- Centralized billing means:
  - Developers don’t expense their own licenses.
  - All charges are consolidated into the Team invoice.
  - When users leave the org, you can revoke their seat centrally.
Lock in ownership and billing contacts
- Set a primary Billing Contact (finance / procurement).
- Keep at least one technical Admin (platform/DevEx) to manage day-to-day usage and onboarding.

At this point, you’ve got the financial plumbing done. Next step: get your developers into the workspace.

Step 3: Invite Developers to Windsurf Teams

With the Team and billing live, you connect your engineers to it.

Invite by email
- In your Team’s Members or Users section, click Invite Members.
- Add corporate email addresses (e.g., @acme.com) for the devs you want in the initial cohort.
- Optionally group invites by team (frontend, infra, data) so you can correlate usage later.
Set default roles
- Designate who is:
  - Admin – can add/remove users, view analytics, manage billing.
  - Member – regular developer seat.
- For a pilot, you might set 1–3 admins (platform/DevEx) and the rest as members.
Send onboarding instructions
- Share a short internal doc or Slack post:
  - Where to download Windsurf.
  - How to sign in with their corporate email.
  - A quick-start: “Open your repo, hit Cmd+I, and try Cascade on a multi-file change.”
Handle existing personal accounts
- If some devs already use Windsurf individually:
  - Have them sign in with the same email and accept the Team invite.
  - Their usage will now be associated with the Team, and billing centralizes automatically.

You now have an org-level Windsurf instance: one bill, many seats, one admin surface.

Step 4: Turn On and Understand Admin Analytics

Admin analytics let you prove that the plan is pulling its weight and help you steer rollout.

Open the admin dashboard
- As a Team admin, go to Admin Dashboard or Analytics in the left nav.
- You’ll see high-level metrics for your Team’s usage.
Key metrics you’ll typically track
While the exact charts evolve, expect views like:
- Active users over time – how many devs are actually using Windsurf.
- Requests or sessions – volume of Cascade conversations, Tab usage, or agent actions.
- Feature adoption – which surfaces are most used (editor, terminal via Cmd+I, browser, Previews, etc.).
Use analytics to guide enablement
- Identify teams or individuals with low usage and run targeted enablement:
  - Short Looms: “How to use Cascade for refactors.”
  - Brown-bag: “From zero to flow state with Tab and Cmd+I.”
- Spot heavy users and capture their workflows as internal best practices.
Connect analytics to outcomes
- Pair Windsurf metrics with:
  - Cycle time for PRs.
  - Time to ship new features.
  - Test coverage or lint errors pre/post rollout.
- This makes the case to expand from pilot to full org adoption.

Admin analytics are read-only from a code standpoint—they don’t change what’s stored from a data retention perspective. They summarize usage, not raw prompt/code logs.

Step 5: Understand Automated Zero Data Retention

For Teams and Enterprise plans, Windsurf enforces automated zero data retention by default for all AI requests. This is the part your security and compliance stakeholders will care about most.

Here’s what that means in practice:

Cloud execution with ZDR:
On Teams:
- AI requests are processed and routed on servers managed by Windsurf (and sometimes subprocessors for model execution).
- For Teams and Enterprise, all inputs and outputs to these AI requests follow zero-data retention policies by default.
- Underlying model providers do not retain your prompts, code, or responses for training or logging.
No training on your data:
- Your org’s code, prompts, and outputs are not used to train shared models.
- ZDR makes this an enforced default, not a config toggle someone might forget.
Scope of ZDR vs analytics:
- ZDR applies to the content passed through models (code, prompts, outputs).
- Admin analytics operate on aggregated usage metadata (e.g., counts, timestamps), not the full text of prompts or responses.
Security posture:
- Windsurf backs this with a broader security framework:
  - SOC 2 Type II
  - FedRAMP High and HIPAA-aligned environments for applicable tiers
  - Hybrid and Self-hosted deployment options available at Enterprise level

For most security teams, the story is: “Our team uses Windsurf’s cloud, but prompts/code are never retained by model providers, and the default for Teams and Enterprise is zero data retention.”

Step 6: Align Teams Setup with Your Security & Governance

Once you understand how Teams handles data, you can formalize Windsurf as an approved tool.

Loop in Security / Compliance
- Share:
  - Windsurf’s Security page (ZDR, SOC 2 Type II, FedRAMP, deployment diagrams).
  - A short summary: “Teams uses cloud execution with automated ZDR by default; no prompts/data retained by model providers.”
Document your internal policy
- Typically you’ll define:
  - What repos or projects can be used with Windsurf.
  - Any restrictions on PII/PHI in prompts (especially in regulated orgs).
  - How to handle third-party services connected via MCP (GitHub, Slack, Stripe, Postgres, etc.).
Prepare for future Enterprise upgrade
- As your org grows, you can move from Teams to Enterprise for:
  - SSO + Access control
  - Role-Based Access Control (RBAC)
  - Hybrid deployment option (via Docker Compose + Cloudflare Tunnel)
  - Dedicated account management and highest priority support
- The Teams setup you’re doing now—billing, analytics, ZDR—forms a clean foundation to justify that upgrade.

Features & Benefits Breakdown

Core Feature	What It Does	Primary Benefit
Centralized Billing	Consolidates all user charges into a single Team invoice.	Simpler procurement, no shadow subscriptions, clean cost visibility.
Admin Dashboard & Analytics	Provides org-level metrics on usage and adoption.	Lets you measure value, guide rollout, and justify expansion.
Automated Zero Data Retention	Ensures AI inputs/outputs use zero-retention policies by default.	Satisfies security/compliance expectations without extra setup.

Ideal Use Cases

Best for pilot rollouts in mid-size engineering orgs: Because Windsurf Teams lets you start with a handful of squads, prove impact (via admin analytics), and keep security happy with automated ZDR.
Best for standardizing AI coding across multiple repos/teams: Because centralized billing, shared policies, and a single Teams workspace mean you can govern how AI is used while developers stay in their preferred IDE workflow.

Limitations & Considerations

No granular RBAC or SSO on Teams alone:
- Fine-grained role-based access control and SSO integrations live on Enterprise.
- If your org requires SSO before rollout, plan to upgrade to Enterprise early.
Cloud-only execution for Teams:
- Teams runs on Windsurf-managed cloud infrastructure.
- If you require Hybrid or fully Self-hosted deployment (e.g., via Docker Compose/Helm behind your firewall), you’ll want Enterprise’s Hybrid/Self-hosted options.

Pricing & Plans

Windsurf offers multiple plan tiers; Teams sits above individual plans and below full Enterprise.

Teams:
- Pricing: listed in current docs as $40 per user / month (always defer to in-product pricing if numbers differ).
- Includes:
  - Everything in Pro
  - Centralized billing
  - Admin dashboard with analytics
  - Priority support
  - Automated zero data retention by default for AI requests
Enterprise:
- Pricing: Let’s talk (custom).
- Includes everything in Teams, plus:
  - Highest priority support
  - Dedicated account management
  - Role-Based Access Control (RBAC)
  - SSO + advanced access control features
  - Hybrid deployment option (with options like Docker Compose + Cloudflare Tunnel and Self-hosted via Helm/Docker Compose)
  - Access to specialized regulated environments (e.g., EU region, FedRAMP High)

If you’re starting at Teams but suspect you’ll need SSO, RBAC, or Hybrid quickly, plan your rollout so you can transition to Enterprise without redoing onboarding.

Frequently Asked Questions

Does Windsurf Teams store my team’s code or prompts?

Short Answer: No—on Teams and Enterprise, AI prompts and outputs follow automated zero data retention by default.

Details:
On Teams, your AI requests are processed in Windsurf’s cloud. For any Teams or Enterprise plan, Windsurf’s default is zero data retention for inputs and outputs to these requests. That means the underlying model providers do not retain or train on your prompts, code, or AI responses. Windsurf uses aggregated usage metadata for admin analytics (counts, timestamps), but not raw prompt text or model outputs, which aligns with security expectations in regulated organizations.

What’s the difference between Windsurf Teams and Enterprise for setup?

Short Answer: Teams gives you centralized billing, analytics, and ZDR; Enterprise adds SSO, RBAC, and advanced deployment options like Hybrid/Self-hosted.

Details:
With Teams, you:

Create a Team workspace.
Attach centralized billing.
Invite users.
Gain access to admin analytics and ZDR by default.

With Enterprise, you keep all of that and gain:

SSO integration (e.g., Okta, Azure AD) and access control features.
Role-based access control for finer-grained permissions.
Hybrid deployment (Windsurf UI + agent in your network) and Self-hosted options.
Dedicated account management and highest priority support.

Most orgs start with Teams for speed, then move to Enterprise once AI is clearly part of their core developer tooling stack.

Summary

Setting up Windsurf Teams is a straight shot: create a Team workspace, attach centralized billing, invite developers, and let admin analytics show you who’s in flow and where to double down. Under the hood, all AI usage on Teams and Enterprise runs with automated zero data retention by default, which makes security sign-off dramatically simpler.

You get one bill, one admin surface, and a developer experience where Cascade and Tab stay in sync with your repos, terminals, and previews—without turning your codebase into model training data. From there, you can scale to Enterprise for SSO, RBAC, and Hybrid/Self-hosted when you’re ready.

Next Step

Get Started