# Cursor Enterprise 推出 Organizations 组织管理功能 - 来源：Cursor Blog - 发布时间：2026-06-03 20:00 - AIHOT 分数：60 - AIHOT 标记：精选 - AIHOT 链接：https://aihot.virxact.com/items/cmpyia45j008gsli3u7h5u1jt - 原文链接：https://cursor.com/blog/organizations ## 精选理由 这是 Cursor 企业版在治理能力上的关键补丁，把多团队预算、模型权限和沙盒测试管了起来，对想把 AI 编程推到千人规模的团队是实打实的基建更新。 ## AI 摘要 Cursor Enterprise 正式推出 Organizations 结构，允许企业在统一面板中管理多个团队。每个团队可独立设置预算、安全策略、模型访问和功能控制。新增 Groups 作为跨团队或团队内的轻量级用户集合，用于分段管理模型访问、花销上限和智能体权限，不同设置取最宽松权限生效。管理员可创建沙箱团队预先测试新功能，再向全公司推送；也可按部门划分模型访问和预算。组织级仪表盘汇总所有团队的 token 用量与花费，支持按团队、用户等维度筛选。身份提供商和 SCIM 目录在组织层面一次配置，成员自动同步。该功能现已全面开放给所有 Enterprise 客户。 ## 正文 Blog / product 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. Jun 1, 2026Product Improvements to Teams Pricing Cursor Team4 min read May 11, 2026Product Updates to Bugbot for Teams and Individuals Cursor Team2 min read Feb 12, 2026Product Expanding our long-running agents research preview Cursor Team5 min read View more posts →