Dear Cursor Team,
We are currently using Cursor with Okta SSO integration through the SAML protocol. Our organization is structured in a way that requires multiple independent teams operating under the same domain (e.g., abc.com), with each team managing its own subscription and corporate billing.
Current Issue
At the moment, when Okta integration is enabled, all users are being routed to a single default team (e.g., teamA), regardless of their intended team association. This limitation makes it difficult to properly onboard users into separate teams such as teamB, even if they belong to a different department or organizational unit.
Example Scenario
Cursor Team ID | Team Name | User
--------------------|---------------|------------------
teamA | Sales Team | [email protected]
teamA | Sales Team | [email protected]
teamB | Dev Team | [email protected]
teamB | Dev Team | [email protected]
Despite the intention to separate these teams in Cursor, new users provisioned through Okta are automatically assigned to teamA, and there is no way to redirect them to teamB via SSO logic or configuration.
Feature Request
We would like to request support for:
- Multiple teams under the same domain within an Okta SAML SSO environment.
- The ability for each team to maintain a separate Business plan and use its own corporate billing method.
- Configurable logic or metadata that allows Okta to route users to the correct Cursor team during provisioning or login.
Why This Matters
For mid-size to large enterprises, this is a critical blocker in adopting Cursor at scale. Many companies operate with a centralized identity domain (e.g., @company.com) while maintaining decentralized budgets and team structures. Without this feature, cross-departmental adoption of Cursor becomes difficult or impossible.
We kindly ask for your consideration and prioritization of this feature, as it would significantly improve the usability and scalability of Cursor in enterprise environments.