Windsurf Guide for Enterprise Admins

Purpose This guide helps enterprise platform / developer-experience administrators plan, roll out, and operate Windsurf for organizations with large enterprise teams. It is intentionally opinionated and links out to detailed “how-to” docs per topic. Treat it both as a read-through guide and as a check-list when onboarding.

1. Audience & Pre-Requisites

Details
Who should readPlatform / Dev-Ex admins, Corporate IT, Centralized Tooling teams
Assumed knowledgeBasic Windsurf terms (team, role), Enterprise IdP concepts (SAML, SCIM), CLI usage
Out-of-scopeDeep security / compliance internals → see Security & Compliance docs

2. Quick-Start Checklist

  1. Confirm organization-wide settings
  2. Set up SSO (Okta, Azure AD, Google; see SAML docs for others)
  3. Enable SCIM & map IdP groups → Windsurf teams
  4. Define role & permission model (least privilege)
  5. Configure Admin Portal: team view & security controls
  6. Distribute Windsurf clients/extensions to end users
  7. View analytics dashboards & API access tokens
Use this list as your “Day 0” deployment tracker.

3. Core Windsurf Concepts

  • Team – flat collections of members; no nested teams. Teams (also called Groups) drive role assignment and analytics grouping, letting you scope permissions and view usage metrics per cohort.
  • Roles & Permissions – predefined RBAC; admins are primarily responsible for team management, Windsurf feature settings, and analytics. Built-in roles usually cover these needs, but creating a custom role with analytics-view permission lets team managers and leads see metrics for their own teams. (RBAC docs)
  • Admin Portal – centralized UI for user & team management, credit usage, SSO configuration, feature toggles (Web Search, MCP, Deploys), analytics dashboards/report export, service keys for API usage, and role/permission controls.
  • Agents & Workspaces – Windsurf IDE and Jetbrains Plugins are Agentic

3.1 Admin Portal Overview

The Admin Portal provides centralized management for all Windsurf enterprise features through an intuitive web interface. Core capabilities include:

User & Team Management

  • Add, remove, and manage users across your organization
  • Configure teams with proper role assignments
  • User status and activity monitoring

Authentication & Security

  • Configure SSO integration with major identity providers
  • Set up SCIM provisioning for automated user lifecycle management
  • Manage role-based access controls (RBAC)
  • Create and manage service keys for API automations with scoped permissions

Feature Toggles & Controls

Important: These feature controls affect behavior for your entire organization and can only be modified by administrators. New major features with data privacy implications are released in the “off” state by default to ensure you have control over when and how they’re enabled.
The Admin Portal gives you granular control over Windsurf features that can be enabled or disabled per team. Data Privacy Note: Some features require storing additional data or telemetry as noted below: Models Configuration
  • Configure which AI models your teams can access within Windsurf
  • Select multiple models for different use cases (code completion, chat, etc.)
Auto Run Terminal Commands (Beta) MCP Servers (Beta) App Deploys (Beta) Conversation Sharing
  • Allow team members to share Cascade conversations with others
  • Conversations are securely uploaded to Windsurf servers
  • Shareable links are restricted to logged-in team members only
  • Learn more about sharing conversations
PR Reviews (GitHub Integration) Knowledge Base Management
  • Curate knowledge from Google Drive sources for your development teams
  • Upload and organize internal documentation and resources
  • Learn more about Knowledge Base

4. Identity & Access Management

Recommendation: Use SSO plus SCIM wherever possible for automated provisioning, de-provisioning, and group management.

4.1 Single Sign-On (SSO)

Guidance
IdPs supportedOkta, Azure AD, Google (others via generic SAML)
Recommended approachCreate Windsurf-specific app in IdP; use role-based group assignments rather than org-wide All Employees group
Common pitfallsEmail suffix mismatches, duplicate user aliases
See the SSO & SCIM Setup Guide for step-by-step configuration for Okta, Azure AD, Google, and Generic SAML. For a standalone SAML walkthrough, see the Generic SAML SSO Guide.

4.2 SCIM Provisioning

  • Why – automated user lifecycle & team membership management at scale
  • Capabilities
    • Create / deactivate users automatically
    • Create teams automatically (or manage manually)
    • Users can belong to multiple teams
    • Custom team creation via SCIM API (docs)
  • Mapping strategies
    • 1 IdP group → 1 Windsurf team (simple, most common)
    • Functional vs. project-based group prefixes (e.g. proj-foo-devs)
  • Things to decide
    • Which groups to exclude (e.g. interns, contractors)
    • Renaming rules when IdP group names change
  • Caution: SCIM should remain your source of truth—mixing SCIM and manual / API updates can create drift. Use the API mainly for adding supplemental groups.

5. User & Team Management at Scale

  • Flat team → design team taxonomy carefully (no nesting to fall back on)
  • Users can belong to multiple groups. Groups are used to view analytics
  • Today, SCIM does not support assigning roles to users. SCIM only supports assigning users to Groups

6. Analytics & API Access

6.1 Built-In Analytics

DashboardUse-case
Adoption OverviewTrack total active users, daily engagement
Team ActivityTeam usage
Analytics shows the percentage of code written by Windsurf, helping quantify impact—see your dashboards at team analytics.

6.2 APIs

APITypical admin scenarios
RESTSCIM management, analytics

7. Operational Considerations

  • Status Pages – monitor live service health: Windsurf, Anthropic, OpenAI
  • Support Channels – windsurf.com/support

8. Setting Up End Users for Success

  1. Point end users to the Windsurf installation guide to install the appropriate extension or desktop client.
  2. Publish an internal “Getting Started with Windsurf” page (link to official docs)
  3. Hold live onboarding sessions / record short demos
  4. Curate starter project templates & sample prompts
  5. Collect feedback via survey after 2 weeks; iterate

9. Additional Resources