要点
Cursor が企業顧客向けに、複数のチームを一元管理し、セキュリティやガバナンス、予算、機能制御を個別に設定できる機能を一般提供開始した。
Enterprise customers can now manage multiple Cursor teams from one place, with different security, governance, budget, and feature controls for each. These capabilities are now generally available to all Enterprise customers.
imageCursor Enterprise organization architecture with organizations, teams, and groups
Organizations
An organization is the top-level container for your company's identity, administration, and membership. It gives admins one place to view and manage their entire Cursor setup, including a rollup of spend and token usage across every team.
Teams
Teams are the operating unit for a department, region, or subsidiary. This is what admins manage as their Cursor org today. We've moved that unit under an organization, so you can run multiple teams, each with its own security, governance, spend, and feature settings.
A user can belong to more than one team, with a different role in each. For current customers, your existing team is preserved and becomes the default home for login, routing, and creating new teams.
Groups
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 more than one team or group, the most permissive setting wins.
Learn more in our announcement post or docs.
改善点 (5)
複数チームのサポートにより、ユーザーは同時に複数のチームに参加可能
組織レベルでの IDP 管理
組織レベルの使用状況分析機能。各チームの詳細なダウングレードも可能
管理者はダッシュボード、API、または CSV を介してユーザーをチーム間で移動可能
新しいユーザーがチームに参加すると、設定と権限が自動的に継承される