Large enterprises, often a complex web of business units and subsidiaries, require distinct controls for budgets, security, and feature access. To address this, Cursor has launched Organizations for Cursor Enterprise, a new structural layer designed to manage multiple Cursor teams from a unified dashboard. This feature, now generally available, allows administrators to set separate budgets, enable varied AI models for different user groups, create sandboxed environments for testing, and monitor company-wide usage analytics.
Related startups
Centralized Control, Decentralized Operation
An Organization serves as the top-level container, consolidating identity, administration, and membership management. Below this sit Teams, the former primary management unit, now nested within an Organization to allow for multiple, independently configured teams. Groups offer a lighter-weight way to manage user cohorts across or within teams, assigning specific model access, spend limits, or agent permissions without the overhead of creating a new team.
The most permissive setting dictates access when a user belongs to multiple teams or groups. For instance, engineering and product teams might have broader network access and automated agent command execution, while sales, marketing, and finance teams could face tighter security controls, particularly concerning agent access to production systems.
Enterprise Use Cases Emerge
Early adopters have highlighted key use cases. Sandboxing new features for security-sensitive teams is a significant pattern, enabling users to test updates in isolated environments before company-wide rollout. This prevents the need for duplicate accounts and allows for rapid iteration without compromising control.
