---
title: "Organizations for Cursor Enterprise"
description: "Cursor has made Organizations generally available to Enterprise customers, enabling them to manage multiple teams from one place. An organization is the top-level container for company identity, administration, membership, and rollups of spend and token usage across teams. Teams remain the operating units for departments, regions, or subsidiaries, but now sit under an organization and can have distinct security, governance, spend, and feature settings. Groups provide lightweight user cohorts across or within teams, with separate model access, spend limits, and agent permissions. A user may belong to multiple teams or groups, and the most permissive setting wins; existing customers retain their current team as the default home for login, routing, and new team creation."
---

# Organizations for Cursor Enterprise

[Cursor](https://yomu.fyi/company/cursor) · Jun 3, 2026

**Type:** Announcement

## Summary

Cursor has made Organizations generally available to Enterprise customers, enabling them to manage multiple teams from one place. An organization is the top-level container for company identity, administration, membership, and rollups of spend and token usage across teams. Teams remain the operating units for departments, regions, or subsidiaries, but now sit under an organization and can have distinct security, governance, spend, and feature settings. Groups provide lightweight user cohorts across or within teams, with separate model access, spend limits, and agent permissions. A user may belong to multiple teams or groups, and the most permissive setting wins; existing customers retain their current team as the default home for login, routing, and new team creation.

## Context

The new hierarchy places an organization above teams, while groups provide a lighter way to manage cohorts across or within teams. Existing customers’ current team is preserved as the default home for login, routing, and creating new teams.

## Approach / What changed

Cursor adds organization-level administration and reporting, team-level controls for security, governance, spending, and features, and group-level controls for model access, spend limits, and agent permissions. Membership and roles can vary by team, while overlapping team or group settings resolve in favor of the most permissive setting.

## Takeaways

- Organizations provide a top-level view of identity, administration, membership, spend, and token usage across every Cursor team.
- Teams can represent departments, regions, or subsidiaries and maintain separate security, governance, spend, and feature settings.
- When users belong to multiple teams or groups, the most permissive setting applies; groups avoid creating a separate team for every cohort.

## FAQ

### How do organizations, teams, and groups differ?

An organization is the company-wide administrative container. Teams are operating units with their own controls, while groups are lightweight user collections that can span or sit within teams.

### Can one user belong to multiple teams?

Yes. A user can belong to more than one team and have a different role in each, and can also belong to multiple groups.

### What happens to an existing customer’s current team?

The existing team is preserved and becomes the default home for login, routing, and creating new teams. It is moved under the organization.

**Tags:** [Cursor](https://yomu.fyi/topic/cursor)

- Source: [Cursor](https://cursor.com/changelog/enterprise-organizations)
- Source URL: https://cursor.com/changelog/enterprise-organizations
- Ingested by Yomu: 2026-09-19T10:36:13.355Z

[Read original post](https://cursor.com/changelog/enterprise-organizations)