Enterprise
Cursor Organizations, Teams and Groups
Cursor Organizations are the top-level enterprise container for identity, administration, membership, spend and usage. Teams sit under the organization, and groups cut across or within teams for model access, spend limits and agent permissions.
What changed in Cursor Organizations, Teams and Groups?
Cursor Organizations are the top-level enterprise container for identity, administration, membership, spend and usage. Teams sit under the organization, and groups cut across or within teams for model access, spend limits and agent permissions.
- Release fact
- Organizations
- Why it matters
- One place to manage identity, administration, membership, spend and token usage across teams.
- Release fact
- Teams
- Why it matters
- Department, region or subsidiary units with their own security, governance, spend and feature settings.
- Release fact
- Groups
- Why it matters
- Cross-team or within-team cohorts for model access, spend limits and agent permissions.
- Release fact
- Most permissive wins
- Why it matters
- When users belong to multiple teams or groups, the most permissive setting applies.
- Release fact
- Operational controls
- Why it matters
- Multi-team membership, org-level IdP, org analytics, API/CSV moves and inherited settings are now supported.
| Release fact | Why it matters |
|---|---|
| Organizations | One place to manage identity, administration, membership, spend and token usage across teams. |
| Teams | Department, region or subsidiary units with their own security, governance, spend and feature settings. |
| Groups | Cross-team or within-team cohorts for model access, spend limits and agent permissions. |
| Most permissive wins | When users belong to multiple teams or groups, the most permissive setting applies. |
| Operational controls | Multi-team membership, org-level IdP, org analytics, API/CSV moves and inherited settings are now supported. |
As of June 23, 2026. See the linked Cursor sources for the latest details.
How should a team use Cursor Organizations, Teams and Groups?
- 1Use Organizations for the company-level admin and identity plane.
- 2Map teams to durable departments, subsidiaries or regions.
- 3Use groups for temporary cohorts, policy exceptions and model or spend differences.
- 4Review effective permissions where users sit in multiple teams or groups.
Interactive diagram. Use Tab to move through hotspots or use the step controls when shown.
What should stay bounded?
Do not model every cohort as a team when a group would preserve simpler administration.
Document when the most-permissive rule gives a user broader access than expected.
Tie spend, usage and model controls to business units before broad rollout.
Frequently asked questions
Who is Cursor Organizations, Teams and Groups for?
Enterprise admins, DevEx leaders, security teams and procurement owners designing Cursor rollout governance.
What makes this page credible?
The guide is grounded in Cursor's June 3, 2026 Organizations changelog and announcement post.
What should I do next?
Start with one real repo task, capture the prompt and review the result before scaling the workflow.
Sources & last verified
- Cursor changelog: Organizations for Cursor Enterprise
- Cursor blog: Introducing organizations for Cursor Enterprise
- Cursor blog: Improvements to Teams Pricing
Cursor ships frequently. Facts verified against primary sources on June 23, 2026.