大型企业通常由众多业务部门、子公司和职能单元组成。我们经常从客户那里听到,这些单元中的每一个都需要各自的预算、安全、治理和功能控制。
为了满足这些需求,我们推出了组织(organizations),这是一种全新的结构,让企业能够在一个地方管理多个 Cursor 团队。借助它,管理员可以为不同团队设置独立的预算,为不同用户群体启用不同的模型,创建沙盒环境来测试新功能,并查看整个公司的使用分析——所有这些都可以在一个仪表盘中完成。
这些能力现已面向所有 Enterprise 客户正式开放。
该结构如何运作
组织是你公司身份、管理和成员关系的顶层容器。这为管理员提供了一个统一的地方来查看和管理其整个 Cursor 配置。
组织之下是团队,即部门或子公司的运营单元。此前,管理员正是在这一层级管理 Cursor。现在,我们将这一单元移至组织之下,以便你可以运行多个团队,每个团队都拥有各自的安全、支出和功能设置。对于现有客户,你已有的团队设置将得到保留。管理员可以在组织层级创建具有独立配置的新团队。
群组是一组轻量级的用户集合,可以跨团队或位于团队内部。它们让用户群体获得独立的模型访问权限、支出限额和智能体权限,而无需新建一整个团队。当用户同时属于多个团队或群组时,以最宽松的设置为准。


在 Cursor,我们为不同部门创建了独立的团队。工程和产品团队拥有最宽松的网络访问权限,并且可以让智能体自动运行命令。销售、市场和财务部门则有更严格的安全管控,尤其是在智能体访问生产系统方面。
企业用例
在测试阶段使用这些新能力的客户中,我们观察到了一些常见的模式。
通过沙箱测试新功能
许多有严格安全审查要求的客户建立了一个预发布团队,可以提前获得 Cursor 新功能的访问权限。这些用户会在沙箱环境中测试功能,然后再将其更广泛地推广到整个公司。
由于一个用户可以属于多个团队,工程师可以在其生产团队中工作的同时保留测试团队的能力,而无需创建第二个 Cursor 账号。
我们设立了一个独立的预发布团队,在新 Cursor 功能向全体工程师广泛发布之前先行试用。我们还有另一个团队,其智能体可以在无需人工批准的情况下自动运行命令。将这两个环境在同一组织下保持相互独立,使我们能够快速推进并采用新能力,而不牺牲控制力。
Wendy Tang
NVIDIA AI 解决方案工程部资深软件工程师
细分模型访问权限、预算与智能体权限
一些客户正在按职能划分模型访问权限和预算。工程、产品和设计职能的用户可以访问所有前沿模型,包括价格更高、带快速模式的选项,以及更高的月度预算。
营销或财务等非产品职能的用户则拥有受限的模型访问权限、更低的预算,并且在智能体能否无需人工审批即可运行命令方面受到更严格的限制。
查看每个团队的详细使用分析
组织仪表盘将支出和 token 用量汇总到每个团队的统一视图中。可按团队、用户、服务账号或云端智能体进行筛选,查看用量来自何处。团队管理员可保留其所属团队的限定视图,这支持按业务单元或成本中心进行费用分摊。
大规模管理身份与成员关系
通过这一结构,客户只需在组织层级配置一次身份提供商和SCIM 目录源。随后,他们便可复用这些工具中的同一批用户群体,在 Cursor 中创建团队和群组,确保成员关系始终保持同步。
管理员可以通过仪表盘、API或 CSV 在团队之间移动用户。当新用户加入团队时,设置和权限会自动生效。
下一步
我们将继续添加更完善的策略控制、更简便的入门流程、由 SCIM 驱动的分配,以及更简单的方式来管理用户子集,而无需将每个工作流都强制拆分到单独的团队中。
Large enterprises are often made up of many business units, subsidiaries, and functions. We frequently hear from customers that each of these units needs its own budget, security, governance, and feature controls.
To support these requirements, we’re introducing organizations, a new structure that allows enterprises to manage multiple Cursor teams from one place. With it, admins can set separate budgets for different teams, enable different models for different cohorts of users, create sandbox environments to test new features, and view usage analytics across the whole company, all from one dashboard.
These capabilities are now generally available to all Enterprise customers.
How the structure works
An organization is the top-level container for your company’s identity, administration, and membership. This gives admins one place to view and manage their entire Cursor configuration.
Under organizations are teams, the operating unit for a department or subsidiary. Admins previously managed Cursor at this level. We’ve now taken this unit and moved it under the organization so you can run multiple teams, each with its own security, spend, and feature settings. For current customers, your existing team setup is preserved. Admins can create new teams with separate configurations at the organization level.
Groups are a lightweight collection of users that can sit across or within teams. They give cohorts of users separate model access, spend limits, and agent permissions without standing up a whole new team. When a user belongs to multiple teams or groups, the most permissive setting wins.


At Cursor, we've created separate teams for different departments. Engineering and product teams have the most permissive network access and the ability to let agents run commands automatically. Sales, marketing, and finance have tighter security controls, especially when it comes to agents accessing production systems.
Enterprise use cases
There are a few common patterns we've seen from customers using these new capabilities in beta.
Sandboxing to test new features
Many customers with strict security review requirements have set up a staging team that gets early access to new Cursor features. These users test features in a sandboxed environment before they are rolled out more broadly to the full company.
Because a user can belong to more than one team, engineers can work in their production team while retaining testing team capabilities without having to create a second Cursor account.
We have set up a separate staging team that tries out new Cursor features before they are released broadly to all our engineers. We have another team where agents can run commands on auto-run without manual approval. Keeping those environments distinct under one organization lets us move quickly and adopt new capabilities without sacrificing control.
Wendy Tang
Staff Software Engineer, AI Solutions Engineering, NVIDIA
Segmenting model access, budgets, and agent permissions
Some customers are segmenting model access and budgets across functions. Users in engineering, product, and design functions get access to every frontier model, including more expensive offerings with fast mode, and higher monthly budgets.
Users in non-product functions like marketing or finance have restricted model access, lower budgets, and tighter restrictions on whether agents can run commands without manual approval.
See detailed usage analytics across every team
The organization dashboard rolls up spend and token usage across every team in one view. Filter by team, user, service account, or cloud agent to see where usage comes from. Team admins keep a scoped view of their own team, which supports chargebacks by business unit or cost center.
Manage identity and membership at scale
With this structure, customers set up their identity provider and SCIM directory source once at the organization level. They can then re-use the same cohorts from these tools to create teams and groups in Cursor, ensuring that membership always stays in sync.
Admins can move users between teams through the dashboard, API, or CSV. And when a new user joins a team, settings and permissions apply automatically.
What's next
We’re continuing to add better policy controls, easier onboarding, SCIM-driven assignment, and simpler ways to manage subsets of users without forcing every workflow into separate teams.
Read more detail on how organizations, teams, and groups work in our docs. Please reach out to our team if you'd like to learn more or have questions.