playbooks

home / skills / jeremylongshore / claude-code-plugins-plus-skills / windsurf-team-settings

windsurf-team-settings skill

/plugins/saas-packs/skill-databases/windsurf/skills/windsurf-team-settings

This skill centralizes Windsurf team settings, enabling organization-wide defaults with team overrides to ensure consistent policy and configuration management.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill windsurf-team-settings

Review the files below or copy the command above to add this skill to your agents.

Files (5)
SKILL.md
1.9 KB
---
name: "windsurf-team-settings"
description: |
  Manage team-wide Windsurf settings and AI policies. Activate when users mention
  "team settings", "organization config", "team policies", "shared settings",
  or "team standardization". Handles team configuration management. Use when working with windsurf team settings functionality. Trigger with phrases like "windsurf team settings", "windsurf settings", "windsurf".
allowed-tools: Read,Write,Edit
version: 1.0.0
license: MIT
author: "Jeremy Longshore <[email protected]>"
---

# Windsurf Team Settings

## Overview

This skill enables centralized management of Windsurf settings across teams and organizations. It covers editor preferences, AI behavior policies, tool approvals, and compliance requirements. Administrators can define organization-wide defaults with team-specific overrides, ensuring consistency while accommodating specialized team needs.

## Prerequisites

- Windsurf Enterprise subscription
- Organization administrator role
- Understanding of team structure and needs
- Compliance requirements documentation
- Team feedback on desired settings

## Instructions

1. **Define Organization Defaults**
2. **Create Team Overrides**
3. **Set Up Policies**
4. **Deploy Settings**
5. **Monitor and Iterate**


See `{baseDir}/references/implementation.md` for detailed implementation guide.

## Output

- Organization-wide settings configuration
- Team-specific override files
- Policy documentation
- Compliance reports

## Error Handling

See `{baseDir}/references/errors.md` for comprehensive error handling.

## Examples

See `{baseDir}/references/examples.md` for detailed examples.

## Resources

- [Windsurf Team Administration](https://docs.windsurf.ai/admin/team-settings)
- [Policy Configuration Guide](https://docs.windsurf.ai/admin/policies)
- [Settings Sync Documentation](https://docs.windsurf.ai/features/settings-sync)

Overview

This skill centralizes management of Windsurf team and organization settings so administrators can enforce consistent defaults while allowing team-specific overrides. It covers editor preferences, AI behavior policies, tool approvals, and compliance controls to reduce configuration drift across teams. Use it to define, deploy, and monitor standardized settings across your organization.

How this skill works

The skill inspects current organization defaults and team-level override files, validates policy rules and tool approvals, and prepares a deployment plan. It can generate policy documentation and compliance summaries, apply settings to target teams, and report discrepancies for iterative updates. Error conditions are surfaced with actionable remediation steps.

When to use it

  • Onboard a new team or workspace and apply organization standards
  • Enforce AI behavior policies and tool approval lists across teams
  • Roll out editor and environment defaults consistently
  • Respond to compliance audits with a standardized settings snapshot
  • Migrate teams when consolidating organization-wide standards

Best practices

  • Start with clear organization defaults and minimal, documented team overrides
  • Collect team feedback before locking critical policies to avoid disruption
  • Use staged rollouts: test on a small team, then expand
  • Keep a versioned change log for settings and policy updates
  • Automate monitoring so configuration drift is detected early

Example use cases

  • Define company-wide AI safety and response policies and push them to all teams
  • Create developer editor defaults and allow product teams to override only allowed fields
  • Approve a set of third-party tools for use and prevent unapproved tool installation
  • Generate a compliance report for auditors showing current settings and recent changes
  • Perform a staged rollout: apply settings to pilot team, gather feedback, then deploy org-wide

FAQ

Who can change team-wide Windsurf settings?

Organization administrators control organization defaults and can grant team admins permission to create approved overrides.

How do I handle exceptions for specialized teams?

Use team-specific override files with narrow scope. Keep overrides documented and reviewed during audits.