Cursor Administrative Set Cap Failing for Some Members

Support Bug Reports
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Unable to set the cap for a member that has exceeded their monthly limit. There are other users under their monthly limit, however I am able to adjust their cap without an issue.

Steps to Reproduce

Cursor.com > Dashboard > Members & Group > Set Cap for a member

Expected Behavior

Expected behavior is I am able to adjust limits for all users.

Operating System

Other

Version Information

Cursor Web

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hey @Jig_Patel, this isn’t something you misconfigured. Right now, members who are also admins of your Cursor organization can’t have their cap changed from the Members page (everyone else saves fine). We’ve let the team know and it’s an issue we’re tracking.

Quick unblock: set their cap via the Admin API (not affected), using a team Admin API key:

curl -X POST https://api.cursor.com/teams/user-spend-limit \
  -u YOUR_API_KEY: \
  -H "Content-Type: application/json" \
  -d '{"userEmail": "[email protected]", "spendLimitDollars": 1000}'

Docs: Set User Spend Limit. I’ll follow up here when there’s an update.

9

Hey @Jig_Patel,

Quick update on this. The failure you hit when saving a cap (the save being rejected with no explanation) has been sorted out on our side.

One thing to be aware of: team members who are also admins of your Cursor organization now show up with an “Org Admin” label on the Members page, and their cap isn’t editable from that page, since org admins are managed at the organization level rather than per team. Caps for everyone else can be set from the Members page as before.

For the org admins specifically, the Admin API route shared above (set user spend limit) remains the way to adjust their cap.

Let me know if you run into anything else.