# Article Name
How to Track and Manage Cursor Premium Seats (3 Methods)

# Article Summary
Manage Cursor premium seats on legacy Teams and The X Subscription. Switch seat types, flag idle seats, and reduce seats in Billing so the charge stops.

# Original HTML URL on Toriihq.com
https://www.toriihq.com/articles/how-to-manage-premium-seats-cursor

# Details
The word "Premium" now names two different Cursor seats, depending on when your team signed up. On a legacy Teams plan, Cursor's Team Pricing docs [https://cursor.com/docs/account/teams/pricing] list Premium at $120 per user a month. New Cursor teams now sign up for The X Subscription, a plan documented by SpaceXSI and managed at grok.com, and there Premium is the $30 entry seat. SpaceXSI's announcement [https://x.ai/news/x-subscription] says the plan opened to new customers on 12 Oct 2026.

Managing Cursor premium seats means deciding who holds the expensive tier, then downgrading or removing the holders who don't use it. Removing a person leaves the charge in place. Stopping it takes a separate Reduce seats step in Billing.

Cursor admins have three ways to do this, and only one, the Members page in Cursor's own dashboard, makes all of these changes. Torii and the Cursor Admin API help you find which seats to change, and the API can remove members on Enterprise.

## Which Cursor Seat Types Does Your Team Have?

The date your team was created decides which seat names you see and where you manage them. Teams created before 12 Oct 2026 keep Standard and Premium seats at cursor.com/dashboard, and can keep adding seats and changing seat types without switching plans. New teams start on The X Subscription, with Free, Premium, Super, and Ultra seats at grok.com/dashboard, the plan's SpaceXSI-run dashboard.

On a legacy team, a Standard seat costs $40 per user a month and a Premium seat $120, with five times the Standard allowance (Cursor Docs, Team Pricing). Annual billing lowers those to $32 and $96, according to Cursor's June 2026 pricing announcement, and a yearly plan can't move to monthly partway through. Our roundup of Cursor contract management tools [/articles/eight-tools-for-cursor-contract-management] covers tracking those annual terms.

The X Subscription prices team seats at $30 for Premium, $100 for Super, and $200 for Ultra, per the same pricing page. Its $0 Free seat carries no team usage allowance and suits admins who manage Cursor without using it, the job the Unpaid Admin seat does on legacy teams.

Cursor's legacy plans page maps legacy Standard to the new Premium and legacy Premium to Super, so the idle seat to hunt is legacy Premium on an older team and Super or Ultra on the new plan. Moving a legacy team to the new plan is optional but permanent. Cursor's help center says Support can't undo the switch.

Source: Cursor Docs, Team Pricing; Cursor blog, 1 Jun 2026 (yearly prices). Checked October 2026.

## Use the Members Page to Manage Cursor Premium Seats

Both seat systems follow nearly the same six steps, and all but the last happen on the Members page of your team's dashboard. Step 6 is the billing change that actually lowers the invoice.

### 1. Open Members in Your Team's Dashboard

Legacy teams find seats under Members at cursor.com/dashboard, and X Subscription teams use Members at grok.com/dashboard. Per Cursor's Members docs [https://cursor.com/docs/account/teams/members], Admins and Unpaid Admins can remove members, change roles, and manage billing, while a Member can invite people but can't remove anyone. Seat tier is separate from role, so one team can mix tiers.

### 2. Review Who Holds Premium Against Their Usage

The Seat Type column sits beside each member's usage in Members, and Usage Analytics holds the same per-member numbers. A Premium holder whose usage would fit inside a Standard allowance is the first downgrade candidate, and on The X Subscription the same check applies to Super and Ultra. Our guide to checking Cursor usage and costs [/articles/how-to-monitor-spending-cursor] shows where each member's numbers sit.

### 3. Switch a Seat Type

Open the Seat Type column (the Seat menu next to each name), choose the new tier, and confirm, which X Subscription admins can do from the member context menu as well. Upgrades take effect immediately with a pro-rated charge. Downgrades wait for the end of the billing period, and picking the current tier again cancels a pending one.

### 4. Set the Seat for New Joiners

A dashboard invite lets an admin pick the tier before the person joins. On The X Subscription, choose Invite under Members, add the emails, then set a Role and a Seat before Send invites. Whoever accepts takes an unused seat, or Cursor buys a new pro-rated one.

People who arrive through SSO or SCIM get no tier choice. A Cursor staff member explained on the Cursor Forum [https://forum.cursor.com/raw/167921]: "They will still join as Standard, then you can bulk-upgrade them to Premium from the dashboard." Cursor's SCIM docs don't mention seat tiers, so select those members on the Members page and change their seat type in one pass.

### 5. Remove a Member Who No Longer Needs a Seat

Legacy admins remove someone from the context menu next to their name, and X Subscription admins choose ⋯, then Remove from team, then Remove access. The person loses team access but keeps their Cursor account and its data. On a legacy team, a member who used any credits holds the seat until the cycle ends, and at least one Admin and one paid member must remain.

On The X Subscription, moving someone to the Free seat instead applies right away, but the paid seat still bills until step 6.

### 6. Reduce Seats in Billing to Stop the Charge

Removing a member only frees the seat for the next hire, and Cursor's Team Pricing page spells out the fix: "Removing a member frees their seat for the next person who joins. Reduce seats in billing to stop paying for it at the end of the period." On The X Subscription, open Billing & invoices, choose Edit seats from the plan menu, then Reduce seats. Legacy teams lower the seat count in Billing as well, though Cursor doesn't document the exact menu path for the older plan.

## Use Torii to Flag Idle Cursor Seats

A monthly seat review in the Cursor dashboard works until the person who runs it gets busy or leaves. Torii reads Cursor seats through its connector and flags the ones with no recent activity. The Cursor admin gets each flag and makes the change in Cursor.

### 1. Start a Free Two-Week Proof of Concept

Request Torii's free two-week proof of concept [/request-a-demo] to get the account Cursor will connect to, and have a Cursor admin ready to create a key.

### 2. Connect Cursor With an Admin API Key

In Torii, open Integrations, choose the Cursor tile, select Connect, enter a Cursor Admin API key, and select Connect again. A green checkbox appears once the sync completes. The Cursor integration help article [https://support.toriihq.com/hc/en-us/articles/37705750122267-Cursor-Integration] lists what the connector reads, which is each user's role, status, and license for one Cursor account. The data refreshes on Torii's daily integration sync.

### 3. Find Idle Cursor Seats and Route Them to the Cursor Admin

Torii's Licenses page lists Cursor licenses and marks a seat Inactive when its holder shows no SSO or browser-extension activity in the inactivity period. That period is 30 days by default, and the same page lists seats still assigned to past employees. Torii syncs a single Cursor license type, so the admin checks which flagged seats are Premium on Cursor's Members page before acting.

A License not in use workflow, with its own inactivity period, sends a Slack or email notice or a Request approval to the Cursor admin. The admin then downgrades or removes the seat in Cursor with steps 3, 5, and 6 above, because the Cursor connector [/integration/cursor] runs no actions of its own.

Usage here comes from SSO sign-ins and browser-extension visits, not time spent in the Cursor editor. If the extension is the only source and fewer than 10 users reported usage in the last 30 days, Torii shows no user activity for the app. Seats that were never used don't fire the trigger, so review those on the Licenses page.

## Use the Cursor Admin API to Find and Remove Idle Seats

The Cursor Admin API returns the team roster and daily activity, enough to script an idle-seat list, though it can't read or change a seat type. Cursor's docs don't say whether X Subscription teams managed at grok.com get the Admin API.

### 1. Authenticate With an Admin API Key

Calls go to https://api.cursor.com with Basic Authentication, sending the key as the username. Any call that changes the team, removal included, needs a key with the admin:* scope.

### 2. List the Roster With /teams/members

A GET /teams/members call returns each member's id, email, name, role, and isRemoved flag, with no seat field. A Cursor staff member on the Cursor Forum [https://forum.cursor.com/raw/164649] wrote that "it does seem like a gap that tier info (which member is on Standard vs Premium) isn't even readable from the Admin API today."

### 3. Find Idle Members With /teams/daily-usage-data

The paginated POST /teams/daily-usage-data call returns every member with an isActive flag for each day, 30 days at most per call (Cursor Admin API docs [https://cursor.com/docs/account/teams/admin-api]). Members with no active day, matched against the Seat Type column, make up your idle Premium list.

### 4. Remove Idle Members With /teams/remove-member

Removal through POST /teams/remove-member is Enterprise only and takes either an email or a userId, at up to 50 requests per minute per team under the same docs. The Enterprise gate is one of the differences covered in our guide to managing Cursor Business and Enterprise plans [/articles/seven-tools-to-manage-cursor-business-and-enterprise-plans]. The response's hasBillingCycleUsage flag shows whether the member had usage this billing cycle, which per Cursor's Members docs keeps the seat occupied until the cycle ends.

Every removal through the API still needs Reduce seats in the dashboard afterward (step 6 of the first method). No documented endpoint changes a seat type.

A small legacy team can get by on the Members page alone, checking the Seat Type column monthly and running Reduce seats after every removal. Enterprise teams that script offboarding can pull the idle list and remove members through the Admin API, though someone still lowers the seat count by hand. Torii fits companies already reviewing licenses across their SaaS stack, since Cursor joins that review while the change still happens in Cursor, and anyone comparing third-party trackers can start with our roundup of tools to track Cursor usage and spend [/articles/six-tools-to-track-cursor-usage-and-spend].