Answer: Admins can move members from manual billing groups by clicking on the billing group and selecting `Move`. For SCIM, billing groups follow identity provider group changes automatically, and for API you use the add members and remove members endpoints to move members programmatically. Status: Confirmed Entry: tool/cursor/admin-and-enterprise/move-members-between-billing-groups Revision: 1 Digest: sha256:bc0690bc6dfc627e (changes whenever the content changes) Timeline: Created: 2026-11-13T03:08:07Z Last changed: 2026-11-13T03:08:07Z Last verified: 2026-11-20T12:31:50Z Next check: 2026-11-21T12:31:50Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Manual method | Move | [1] | 2026-11-20 SCIM behavior | the billing group follows those changes automatically | [1] | 2026-11-20 API method | add members | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/account/enterprise/billing-groups.md". https://cursor.com/docs/account/enterprise/billing-groups.md Role: primary. Accessed: 2026-11-20T12:31:50Z Quote: "Admins can move members from manual billing groups by clicking on the billing group and selecting `Move`." (Supports: Manual method) Quote: "When members are moved between SCIM groups in your identity provider, the billing group follows those changes automatically." (Supports: SCIM behavior) Quote: "Use the [add members](https://cursor.com/docs/account/teams/admin-api.md#add-members-to-group) and [remove members](https://cursor.com/docs/account/teams/admin-api.md#remove-members-from-group) endpoints to move members programmatically." (Supports: API method) Snapshot SHA-256: 3d16d40616129ff978924c168abc241bba776f40b8c36464cfef789186948711 (captured 2026-11-13T03:08:07Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:08:07Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:31:50Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:31:50Z Last attempt: 2026-11-20T12:31:50Z Notes and limitations: Extracted automatically from a single official source (section "Move members between billing groups"). Related: https://latestn.com/tool/cursor/admin-and-enterprise/opentelemetry-export-limitations What are the limitations of Cursor OpenTelemetry Export? https://latestn.com/tool/cursor/admin-and-enterprise/opentelemetry-export-prerequisites What are the prerequisites and source IP requirements for Cursor OpenTelemetry Export? https://latestn.com/tool/cursor/admin-and-enterprise/org-level-sso-setup How do I set up organization-level SSO for Cursor Enterprise? https://latestn.com/tool/cursor/admin-and-enterprise/mcp-enterprise-controls What enterprise admin controls does Cursor provide for MCP servers? https://latestn.com/tool/cursor/admin-and-enterprise/mdm-policies What MDM policies can I enforce for Cursor, such as allowed team IDs and extensions? https://latestn.com/tool/cursor/admin-and-enterprise/minimum-versions What are the minimum versions required for Cursor deployment features? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:08:07Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/admin-and-enterprise/move-members-between-billing-groups/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/admin-and-enterprise/move-members-between-billing-groups POST: https://latestn.com/dispute/tool/cursor/admin-and-enterprise/move-members-between-billing-groups with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/admin-and-enterprise/move-members-between-billing-groups?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I move Cursor users between billing groups? Revision 1, last verified 2026-11-20T12:31:50Z. https://latestn.com/tool/cursor/admin-and-enterprise/move-members-between-billing-groups (accessed 2026-11-21T10:02:50Z). @misc{LatestN_tool_cursor_admin_and_enterprise_move_members_between_billing_groups_r1, title = {How do I move Cursor users between billing groups?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/admin-and-enterprise/move-members-between-billing-groups}}, note = {Revision 1; digest sha256:bc0690bc6dfc627e; last verified 2026-11-20T12:31:50Z; accessed 2026-11-21T10:02:50Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/admin-and-enterprise/move-members-between-billing-groups