Configure set up Cursor for teams and organizations. Triggers on "cursor team", "cursor organization", "cursor business", "cursor enterprise setup". Use when working with cursor team setup functionality. Trigger with phrases like "cursor team setup", "cursor setup", "cursor".
npxskills add jeremylongshore/claude-code-plugins-plus-skills--skill cursor-team-setupLoading…
Configure Cursor for teams and organizations. Covers plan selection, member management, shared configurations, Privacy Mode enforcement, and onboarding workflows.
| Feature | Pro ($20/user/mo) | Business ($40/user/mo) | Enterprise (custom) |
|---|---|---|---|
| Fast requests | 500/mo | 500/mo/seat | Custom |
| Tab completion | Unlimited | Unlimited | Unlimited |
| Privacy Mode | Optional | Enforced by default | Enforced |
| SSO (SAML/OIDC) | No | Yes | Yes |
| SCIM provisioning | No | No | Yes |
| Admin dashboard | No | Yes | Yes |
| Usage analytics | No |
| Yes |
| Yes (advanced) |
| Priority support | No | No | Yes |
| Dedicated account mgr | No | No | Yes |
| SLA | No | No | Yes |
| SOC 2 report access | No | Request | Included |
Admin Dashboard (Business/Enterprise):
Dashboard Sections:
├── Members → Invite, remove, assign roles
├── Usage → Request counts, model usage, costs
├── Privacy → Privacy Mode enforcement
├── Models → Restrict available models
├── SSO → SAML/OIDC configuration
└── Billing → Plan, invoices, seat management
Methods:
1. Email invitation: Admin dashboard > Members > Invite by email
2. Domain auto-join: Allow anyone with @company.com to join
3. SSO provisioning: Users auto-join when they sign in via SSO
4. SCIM (Enterprise): Automatic sync from identity provider
Roles:
| Role | Permissions |
|---|---|
| Owner | Full admin, billing, delete org |
| Admin | Manage members, settings, SSO |
| Member | Use Cursor with team settings |
For Business and Enterprise plans:
Privacy Mode guarantees:
Admin Dashboard > Models:
Available models (toggle on/off per team):
✅ GPT-4o
✅ Claude Sonnet
✅ Auto mode
❌ Claude Opus (restricted to save costs)
❌ o1 (restricted to save costs)
✅ cursor-small
Restricting models helps control costs -- premium models consume fast requests faster.
Team settings that belong in the project repository:
.cursor/rules/
├── project.mdc # Stack, conventions (alwaysApply: true)
├── security.mdc # Security constraints (alwaysApply: true)
├── code-style.mdc # Naming, formatting (alwaysApply: true)
├── typescript.mdc # TS patterns (glob: **/*.ts)
├── react.mdc # React patterns (glob: **/*.tsx)
└── testing.mdc # Test conventions (glob: **/*.test.ts)
Commit these to git. Every team member gets the same AI behavior.
.cursorignore # Shared exclusions (commit to git)
.cursorindexingignore # Shared indexing exclusions (commit to git)
These are NOT shared via git:
settings.json (editor preferences -- personal choice)keybindings.json (keyboard shortcuts -- personal choice)## New Team Member: Cursor Setup (20 minutes)
### Account
[ ] Download Cursor from cursor.com/download
[ ] Sign in with @company.com email
[ ] Verify Business plan active (cursor.com/settings)
[ ] Verify Privacy Mode is ON (Cursor Settings > General)
### Project Setup
[ ] Clone the repository
[ ] Open in Cursor: `cursor /path/to/project`
[ ] Wait for indexing to complete (bottom status bar)
[ ] Verify rules loaded: Cmd+L > type "@Cursor Rules"
### Learn the Basics (10 min)
[ ] Tab completion: type code, accept with Tab
[ ] Chat: Cmd+L > "@Codebase how is auth handled?"
[ ] Inline Edit: select code > Cmd+K > "add error handling"
[ ] Composer: Cmd+I > describe a multi-file task
### Team Conventions
[ ] Read .cursor/rules/ files (our AI guidelines)
[ ] Use Conventional Commits for commit messages
[ ] Start new chats for new tasks (don't reuse old conversations)
[ ] Review all AI-generated code before committing
Pair new team members with experienced Cursor users for their first week. Focus areas:
@ context| Metric | Purpose |
|---|---|
| Requests per user | Identify power users and underutilizers |
| Model distribution | Which models are used most |
| Fast vs slow requests | Quota consumption rate |
| Cost per seat | ROI calculation |
High adoption:
- 80%+ team members active weekly
- Average 10+ requests/day per user
- Rules files regularly updated in git
Low adoption (needs attention):
- Team members not signing in
- Rules files stale or absent
- No AI commit messages in git history
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).