# Introducing organizations for Cursor Enterprise

Source: [Cursor](https://cursor.com/blog/organizations)  
Feed7 permalink: https://feed7.dev/p/organizations-1ecywn3  
Published: Unknown  
Trust: Official Source (official_source)

## Why Included

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.

## Source Summary

**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.

## Practical Implication

**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.

## Agent-Ready Context

**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.

## Context Map

- Layer: tools
- Domains: coding
- Topics: dev-ux, enterprise

## Uncertainty

- 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.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.