Organizations for Cursor Enterprise

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.

Takeaways

1. 1

   Organizations provide a top-level view of identity, administration, membership, spend, and token usage across every Cursor team.

2. 2

   Teams can represent departments, regions, or subsidiaries and maintain separate security, governance, spend, and feature settings.

3. 3

   When users belong to multiple teams or groups, the most permissive setting applies; groups avoid creating a separate team for every cohort.

FAQ