Cursor Business SSO 席位与离职交接：采购合同必须写清这些
内容刷新 / GEO：补 English summary 与最新核对清单 — ch-cursor-business-sso-team
All guides · Full article is primarily Simplified Chinese; use the English summary below for quick takeaways (GEO-friendly).
## Cursor Business SSO 席位与离职交接：采购合同必须写清这些
当贵公司使用 Cursor Business（Teams 或 Enterprise 计划）时，SSO（单点登录）和 席位管理 是日常运营的核心。离职员工交接时，如果合同未明确说明席位转移、回购条款或自动 deprovision，容易导致账号残留、合规风险或额外支出。采购合同必须写清这些条款，才能让工程师和采购团队在决定“订不订 Cursor Business”时直接对照，避免后续争议。
贵公司适用场景包括：已有 SSO（如 Okta、Azure AD）的中大型团队；需要 SCIM 自动同步的用户生命周期；或已签 PO/发票计费的 Enterprise 计划。这类情况必须在合同中约定席位回收机制，否则按员工离职节奏手动处理会增加 IT 负担。
现状与数据更新
2026 年 10 月，Cursor Business 计划已将 SCIM 席位管理列为 Enterprise 标配。Teams 计划支持 SAML/OIDC SSO 与按席位计费（$40 / user / mo. 起），Enterprise 计划则提供 SCIM、池化使用量和 PO 发票模式。 [[1]](https://cursor.com/pricing) [[2]](https://cursor.com/docs/enterprise/identity-and-access-management.md)
根据官方定价页和 IAM 文档，SSO 需优先配置，SCIM 可实现新员工自动添加、离职自动移除。2026 年 9 月更新后，企业用户可通过组织级身份管理（Organizations）统一处理多团队环境，减少手动维护。
核对清单
采购合同需明确以下要点（按优先级排序）：
| 条款类别 | 必须写入内容 | 风险（未写明） |
|---|---|---|
| 席位归属权 | 明确席位（seats）是否归公司所有；离职后是否自动回收或需回购 | 残留账号导致超额计费 |
| 自动 deprovision | 是否支持 SCIM 或 SAML 自动移除；离职员工退出 IdP 后 Cursor 是否立即失效 | 账号残留、安全漏洞 |
| 回购条款 | 合同期内席位是否可回购；回购价是否等于剩余合同期；最小回购数量 | 跳槽员工复用导致额外支出 |
| 离职交接流程 | 谁负责（IT/HR）；需多久内通知；是否支持席位转移到新员工 | 手动处理延误、审计不合规 |
| 合规与审计 | 是否需审计日志（audit logs）；离职后 30/60 天内确认 deprovision | 监管罚款或合规违反 |
| 升级与变更 | 新计划席位是否自动迁移；SSO 切换成本与通知期 | 计划升级后席位管理中断 |
该清单可直接复制到采购模板中，便于律师和采购团队快速验证。
风险边界
未写清席位归属权的合同，离职员工可能在合同期内继续使用，导致按席位计费超出预算。SCIM 未启用时，SaaS 行业常见问题是 session 残留或 refresh token 无法立即撤销。
重要声明：本文仅为参考，不能替代法律意见。请咨询专业律师和 Cursor Business 销售团队，以官方/挂牌页最新数据为准。
站内路径
English summary
Cursor Business SSO seat management and offboarding: what your purchase contract must specify.
When your company subscribes to Cursor Business (Teams or Enterprise plans), SSO and seat control are essential for daily operations. If the contract does not clearly define seat transfer, repurchase terms, or automatic deprovisioning during employee departures, it can result in lingering accounts, compliance risks, or extra costs. Contracts must cover these points to help engineering and procurement teams evaluate “buy or not” and avoid future disputes.
This guide covers applicable scenarios such as teams with SSO providers like Okta or Azure AD, companies needing SCIM for user lifecycle automation, or those already on PO/invoice billing Enterprise plans. These situations require explicit contract clauses for seat reclamation mechanisms, or manual handling per resignation timeline increases IT workload.
As of October 2026, Cursor Business plans make SCIM seat management a standard Enterprise feature. Teams plans support SAML/OIDC SSO with per-seat billing starting at $40/user/month, while Enterprise adds pooled usage, SCIM, and PO billing. As of the September 2026 update, organizations can use organization-level identity management (Organizations) to handle multiple teams efficiently and reduce manual maintenance.
核对清单
The contract checklist includes seat ownership, automatic deprovisioning support, repurchase terms, offboarding process timelines, compliance and audit requirements, and plan upgrade rules.
| Category | What must be written | Risks if not specified |
|---|---|---|
| Seat ownership | Clearly define if seats belong to the company; automatic recycling or repurchase on termination | Residual accounts leading to over-billing |
| Automatic deprovision | Support for SCIM or SAML auto-removal; immediate cursor access revocation after IdP removal | Residual accounts, security vulnerabilities |
| Repurchase terms | Repurchase eligibility during contract; repurchase price and minimum quantity | Extra costs from employee jumps |
| Offboarding process | Who (IT/HR) handles; notification deadline; seat transfer to new employee | Manual delays, audit issues |
| Compliance & audit | Audit logs required; deprovision confirmation within 30/60 days | Regulatory fines or violations |
| Upgrade & change | Automatic seat migration on plan change; SSO switch notification period | Interruption in seat management |
风险边界
Contracts without clear seat ownership can cause departing employees to continue using accounts within the contract period, leading to over-billing under per-seat pricing. Without SCIM, common SaaS issues include session persistence or unrevoked refresh tokens.
Important disclaimer: This is for reference only and not a substitute for legal advice. Please consult a professional lawyer and Cursor Business sales team, using the latest data from official/quoted pages.