Enterprise
Cursor Organization Groups: Cross-Team Cohorts for Admins
Organization Groups let Cursor Enterprise admins organize users across teams in the same Organization into cohorts like Engineering, Contractors, or Pilot Users. Each group can carry shared settings, including per-user spend limits and model access, that combine with team settings using a permissive model. Groups can be managed manually or synced from your identity provider through SCIM, and they are separate from Billing Groups, which only attribute spend.
On this page
What are Cursor Organization Groups?
Organization Groups gather people from different teams into one cohort when the same set of users needs shared settings. They are not the same thing as Billing Groups: Billing Groups help a team report and attribute spend, while Organization Groups manage organization-level cohorts and the settings that apply to them.
Use Organization Groups to apply model access or usage controls to a cross-team cohort, to manage a group from your identity provider through SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave., to give a pilot group early access to a new model before a wide rollout, to keep team defaults strict while widening access for specific users, and to manage membership through the Organization API.
How do you create an Organization Group?
In the dashboard, open your Organization and go to Groups. Cursor supports two kinds of group, and the choice decides where membership is managed.
Admins add, remove, import, and move members in the dashboard or through the Organization API.
Best when membership does not mirror a directory group.
Cursor maps the group to a directory group from your identity provider.
Membership is managed in your IdP and synced into Cursor; manual membership changes are disabled because the next sync would overwrite them.
How do you manage group members?
Open a group and select Members to view and manage membership. What you can do depends on whether the group is manual or SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave.-synced.
- Manual groups: add existing Organization members, import members by CSV, move members to another group, remove members, and search and sort the list.
- SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave.-synced groups: membership is read-only, but admins can still manage Cursor-owned settings such as spend limits and model access.
What settings can a group carry?
Open a group and select Settings to manage group-level controls. Cursor documents three: per-user spend limits, model access, and agent and model-routing controls. The recurring pattern is permissive combination, set restrictive defaults at the team level and widen access for chosen cohorts at the group level.
- Setting
- Spend limits
- What it controls
- Per-user monthly spend limits.
- How it combines
- Cursor applies the most permissive applicable limit across a user's groups and team.
- Setting
- Model access
- What it controls
- Which models the group can use, set on the Models tab.
- How it combines
- Group settings combine with team settings permissively; widen access per cohort over a strict team default.
- Setting
- Auto-run and Smart Auto
- What it controls
- Group-level agent and model-routing controls where available.
- How it combines
- Team-level restrictions still matter; a team that blocks a model can affect the user.
| Setting | What it controls | How it combines |
|---|---|---|
| Spend limits | Per-user monthly spend limits. | Cursor applies the most permissive applicable limit across a user's groups and team. |
| Model access | Which models the group can use, set on the Models tab. | Group settings combine with team settings permissively; widen access per cohort over a strict team default. |
| Auto-run and Smart Auto | Group-level agent and model-routing controls where available. | Team-level restrictions still matter; a team that blocks a model can affect the user. |
Group settings combine with team settings using a permissive model, per Cursor's docs.
If a team default is stricter and a group has a higher spend limit, the group limit applies to that user. A group limit lower than an already more permissive team setting does not make access stricter. And because groups span teams, a user's team-level block on a model can still affect their experience even when the group allows it.
How do SCIM and the Organization API fit in?
SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. lets your identity provider decide who belongs to a group, which Cursor recommends when the group mirrors an existing department, role, or access cohort. Before mapping SCIM groups, make sure SCIM provisioning is configured for your Organization, then connect the Organization Group to the matching directory group. Group membership can also be read and changed through the Organization API.
You can list groups, read members, and add or remove members through the Organization API. Organization Group API routes use Organization API keys and group IDs with the g_ prefix. Organization Groups are available on Enterprise.
Frequently asked questions
Are Organization Groups the same as Billing Groups?
No. Billing Groups help a team report and attribute spend. Organization Groups manage cross-team cohorts and the settings that apply to them, such as spend limits and model access.
Can I sync an Organization Group from my identity provider?
Yes. SCIM-synced groups map to a directory group in your IdP, where membership is managed and synced into Cursor. Manual membership changes are disabled for synced groups, but admins still control Cursor-owned settings.
How do group spend limits combine with team limits?
Cursor applies the most permissive applicable limit. A higher group limit overrides a stricter team default; a lower group limit will not make an already more permissive team setting stricter.
Sources & last verified
Cursor ships frequently. Facts verified against primary sources on June 26, 2026.