Introducing organizations for Cursor Enterprise

Summary

Cursor is introducing organizations, a top-level structure that lets Enterprise customers manage multiple teams, budgets, security policies, governance, and feature controls from one dashboard. Organizations contain teams for departments or subsidiaries and groups for user cohorts; separate configurations can govern model access, spending, agent permissions, and network access, while the most permissive setting applies when users belong to multiple teams or groups. The organization dashboard aggregates spend and token usage across teams and supports filtering by team, user, service account, or cloud agent, while identity-provider and SCIM setup is centralized and membership can be managed through the dashboard, API, or CSV. Generally available to all Enterprise customers, the structure supports sandbox teams for testing features, scoped administration and chargebacks, and differentiated controls across functions; Cursor says policy controls, onboarding, and SCIM-driven assignment are still being expanded.

Takeaways

1. 1

   Teams can have separate security, spending, model-access, and feature settings, while groups provide cohort-level controls without requiring a separate team.

2. 2

   The organization dashboard rolls up spend and token usage across teams and supports filtering by team, user, service account, or cloud agent; team admins retain scoped views for chargebacks.

3. 3

   Users can belong to multiple teams or groups, allowing production and sandbox access under one account; when settings overlap, the most permissive setting wins.