Introducing organizations for Cursor Enterprise
Cursor Enterprise adds organizations: a teams-within-org hierarchy with per-team budgets, model access controls, and spend and token analytics rolled up in one admin dashboard.
**The gist** Cursor shipped **organizations** for Enterprise plans on **June 3, 2026**: an org contains teams, teams contain users, and admins manage it all from one dashboard with **separate budgets per team**, per-cohort model access, and rolled-up spend and token analytics. Identity provider and **SCIM** integration sit at the org level; users move via dashboard, API, or CSV.
**Why it matters** If you run Cursor across teams or clients, you can now scope **model access and agent permissions** per group and designate **sandbox teams** to trial features before wide rollout. Users can belong to several teams at once, and **the most permissive setting wins** — worth knowing when you reason about access.
**The gist** Cursor shipped **organizations** for Enterprise plans on **June 3, 2026**: an org contains teams, teams contain users, and admins manage it all from one dashboard with **separate budgets per team**, per-cohort model access, and rolled-up spend and token analytics. Identity provider and **SCIM** integration sit at the org level; users move via dashboard, API, or CSV. **Why it matters** If you run Cursor across teams or clients, you can now scope **model access and agent permissions** per group and designate **sandbox teams** to trial features before wide rollout. Users can belong to several teams at once, and **the most permissive setting wins** — worth knowing when you reason about access. **Watch out** This is **Enterprise-only**, so solo builders and small teams get nothing directly. Policy controls, simpler onboarding, and **SCIM-driven assignment** are still listed as in development.