Cursor Launches Organizations to Manage Multiple Enterprise Teams

Large companies often consist of multiple divisions, branches, and functional departments — each with their own needs for access management, budgeting, and security rules. Cursor has introduced Organizations — a new management structure that allows Enterprise customers to control multiple Cursor teams from one place, with separate budgets, security, and access rights for each division.

How Organizations Structure Works

Organizations operates on a three-level hierarchy that provides flexibility for companies of any size. At the top level is the organization itself — a container for managing the entire company. Administrators see a unified control panel here for managing settings, security, and access rights to all resources.

Below the organization are Teams — these are operational units for company departments or branches. Each team can have its own budget, its own set of available AI models, and rules for agent automation. Previously, administrators managed Cursor at the team level. Now this unit has moved under Organizations, allowing multiple independent teams to operate within one organization.

The third level is Groups. These are lightweight sets of users that can overlap between teams or within a single team. Groups give specific employee cohorts restrictions on model access, spending limits, and control over automatic agent commands — all without needing to create a separate team. When a user belongs to multiple teams or groups, the most permissive of these rules apply.

How It's Used in Practice

At Cursor itself, Organizations is used to divide access by departments. Engineers and product teams get maximum permissions — they can use all frontier models and allow agents to execute commands in automatic mode. The sales, marketing, and finance departments operate under stricter security restrictions, especially regarding agent access to production systems.

Several popular use cases have emerged among beta customers:

• Sandbox for Safe Testing — a separate isolated team gets early access to new Cursor features before their release to the entire company. Engineers remain in the main production team and don't need to create a second account, which simplifies license management.
• Different Models for Different Functions — engineering and product see all frontier models, including the most expensive options with fast mode and high monthly limits. Sales and finance have access only to basic models, with lower budgets and restricted automatic agent commands.
• Unified Spending Analytics — the Organizations dashboard shows spending and token usage across all teams in one view. You can filter data by team, user, service account, or cloud agent, while local administrators see only their team for accounting purposes.

"We've set up a separate staging team that tests new Cursor features before releasing them to all engineers.

Another team allows agents to execute commands in automatic mode without approval. Separating these environments under one organization lets us quickly implement new capabilities without compromising control," — Wendy Tang, Staff Software Engineer at NVIDIA.

Identity Management at Scale

Organizations allows you to configure your identity provider and SCIM synchronization once at the organization level, then reuse these user cohorts to create separate teams and groups. This significantly simplifies access rights management in large companies and reduces the burden on IT administrators.

What This Means

Organizations makes Cursor a much more flexible tool for large companies that need detailed control over AI model access, budgeting by department, and isolation of test environments from production. For startups and small teams, the existing Teams structure remains the primary way to organize work.