Workflow: Team Collaboration

Overview

This workflow covers setting up Cursor for team collaboration, including shared rules, documentation, and consistent AI behavior across your organization.

When to Use: Onboarding new team members, standardizing practices, sharing knowledge

---

Prerequisites

• Cursor Team or Enterprise subscription
• Admin access (for team settings)
• Git repository for version control

---

Workflow Diagram

Step	Action	Description
1	Set Up Team	Create team, invite members, assign roles
2	Configure Team Rules	Define coding standards and enforce them
3	Create Project Rules	Version-controlled rules in .cursor/rules
4	Set Up Shared Docs	@Docs accessible to all team members
5	Onboard Members	Share guides and best practices

---

Step 1: Set Up Team

Create Team

1. Go to cursor.com/dashboard
2. Click "Create Team"
3. Enter team name
4. Choose plan (Team or Enterprise)

Invite Members

1. Dashboard → Team → Members
2. Click "Invite Members"
3. Enter email addresses
4. Assign roles:
   • Admin: Manage settings and members
   • Member: Use team features

Configure SSO (Enterprise)

For seamless authentication:

1. Dashboard → Settings → SSO
2. Configure with your IdP (Okta, Azure AD, etc.)
3. Enable for team

---

Step 2: Configure Team Rules

Team Rules ensure consistent AI behavior across all members.

Create Team Rule

1. Dashboard → Team Content → Rules
2. Click "Add Rule"
3. Write your rule:

# Team Coding Standards

## Required
- Use TypeScript for all new code
- Follow our internal API patterns
- Add tests for new functionality
- Use our logging library, not console.log

## Preferred
- Functional components in React
- Hooks over class components
- Async/await over Promise chains

## Forbidden
- No hardcoded secrets
- No direct database queries in controllers
- No any types without justification

4. Enable "Enforce this rule" for mandatory compliance

---

Step 3: Create Project Rules

Project Rules live in the repository and are version-controlled.

Set Up Rules Directory

.cursor/
└── rules/
    ├── code-style/
    │   └── RULE.md
    ├── api-patterns/
    │   ├── RULE.md
    │   └── templates/
    │       └── endpoint.ts
    └── testing/
        └── RULE.md

Example: API Patterns Rule

.cursor/rules/api-patterns/RULE.md:

---
description: "Patterns for creating API endpoints"
globs: ["src/api/**/*.ts", "src/routes/**/*.ts"]
alwaysApply: false
---

# API Patterns

When creating API endpoints, follow these patterns:

## Request Validation
Always validate incoming data using our Zod schemas:
@templates/validation.ts

## Error Handling
Use our standard error handler:
@templates/error-handler.ts

## Response Format
{
  "success": boolean,
  "data": object | null,
  "error": string | null
}

Share via Git

git add .cursor/rules
git commit -m "Add project rules for team"
git push

All team members get the rules when they pull.

---

Step 4: Set Up Shared Documentation

Add Internal Documentation

1. In Cursor: Type @Docs in chat
2. Select "Add new doc"
3. Add your internal documentation URL
4. Enable "Share with team"

Common Documentation to Add

Documentation	URL
Internal API Docs	https://docs.internal.company.com/api
Style Guide	https://docs.internal.company.com/style
Architecture	https://docs.internal.company.com/architecture

Manage Documentation

Dashboard → Cursor Settings → Indexing & Docs

• View all shared documentation
• Edit or remove as needed
• See which docs are team-shared

---

Step 5: Onboard Team Members

Create Onboarding Guide

Share this with new team members:

# Cursor Team Setup

## 1. Install Cursor
Download from cursor.com/downloads

## 2. Join Team
Accept the team invitation email

## 3. Configure
- Sign in with your company credentials (SSO)
- Open your project in Cursor

## 4. Verify Team Features
- Check Team Rules appear in Cursor Settings
- Verify shared @Docs are available
- Confirm project rules apply

## 5. Learn the Tools
- Tab: Autocomplete (accept with Tab)
- Cmd+K: Inline edit
- Cmd+I: Agent chat

## 6. Key Shortcuts
- Cmd+. : Switch modes
- Cmd+/ : Change AI model
- @ : Add context to prompts

Team Training Session

Cover these topics:

1. Cursor basics: Tab, Inline Edit, Agent
2. Team rules: What they are, how they help
3. Shared documentation: How to use @Docs
4. Best practices: When to use which tool

---

Maintaining Team Consistency

Regular Rule Reviews

Monthly:

• [ ] Review Team Rules effectiveness
• [ ] Check for outdated patterns
• [ ] Gather feedback from team

Quarterly:

• [ ] Audit project rules across repositories
• [ ] Update documentation references
• [ ] Review and refresh shared docs

As Needed:

• [ ] Add rules for new patterns
• [ ] Remove deprecated practices
• [ ] Update after tech stack changes

Share Best Practices

Create a Team Rules for sharing knowledge:

# Knowledge Sharing

When you solve a tricky problem:
1. Consider if it could help others
2. If so, suggest a project rule
3. Document patterns in our internal wiki
4. Share in #cursor-tips Slack channel

---

Best Practices

Rules

• Keep rules focused and under 500 lines
• Version control project rules
• Use Team Rules for organization-wide standards
• Use Project Rules for repo-specific patterns

Documentation

• Share commonly-used documentation
• Keep internal docs up to date
• Use @Docs in prompts for consistency

Onboarding

• Create clear setup guides
• Buddy system for new members
• Regular check-ins during first weeks

---

Related SOPs

• SOP-010: Project Rules
• SOP-015: Team & Enterprise
• SOP-011: @ Mentions