Permission Regression: Team Members Lose Access to Their Own Spending Page When Admin-Only Usage Settings Is Enabled

Support Bug Reports
1

Hi Cursor team,

This appears to be a permission regression / incorrect permission coupling in Cursor Teams.

When an administrator enables:

Only Admins Can Edit Usage Settings

regular team members lose access to their own Spending / Included Usage page:

This behavior does not make sense.

The purpose of “Only Admins Can Edit Usage Settings” should be to prevent members from changing usage-related settings, especially enabling On-Demand Usage without administrator approval.

It should not prevent members from viewing their own usage data.

These are two completely different permissions:

  • Write permission: Enable On-Demand Usage, change spending settings, modify usage controls.
  • Read permission: View personal included usage, consumed quota, and remaining allowance.

There is no reasonable security or administrative justification for removing read-only visibility simply because members are not allowed to edit usage settings.

In its current form, administrators are forced to choose between two bad options:

  1. Allow members to access usage settings, which also gives them more control than the administrator may want.
  2. Restrict usage settings, but then prevent members from even seeing their own consumption.

For a Team product, this is a poor permission model.

Members need to know how much quota they have consumed. Without access to their own Spending page, they cannot tell whether they are approaching their included usage limit and must repeatedly ask an administrator to check on their behalf.

The expected behavior should be straightforward:

Only Admins Can Edit Usage Settings = ON

  • Members cannot enable On-Demand Usage.
  • Members cannot change spending or usage settings.
  • Members cannot modify workspace-level usage controls.
  • Members can still view their own Spending / Included Usage information in read-only mode.
  • Administrators retain full control over all editable usage settings.

Please treat this as a permission bug rather than a feature request.

The ability to view personal usage should not be tied to the ability to edit usage settings. These permissions should be separated.

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

6

Hey @rebermusk, thanks for the report.

This is currently working as designed rather than a permissions slip. The Spending page is where the editable usage controls live (the On-Demand toggle and spend limits), so when “Only Admins Can Edit Usage Settings” is turned on, that whole page is restricted to admins instead of being shown read-only.

Members can still see their own consumption in the Usage page on the dashboard, which shows their requests and included usage for the current cycle,

8

Thanks — I understand what you mean now. I found the Usage page you were referring to, and you’re right that members can see their own consumption there once usage has been generated.

However, I still think there is a UX / visibility gap here that would be worth improving.

The current Usage page is not equivalent to the Spending / Included Usage view available to personal users and Team admins.

There are a few important differences:

  • Before a member has generated any usage, the Usage page can appear essentially empty, so there is no clear indication of what quota they actually have available.
  • It shows historical/current consumption, but does not provide the same clear quota progress bars as the Spending page.
  • The Grok Bot weekly usage quota / percentage is not shown there.
  • Members cannot easily see, at a glance, how much of each included quota remains.

What I would ideally like is for Team members to have a read-only version of the same Included Usage panel that personal users and Team admins currently see on the Spending page.

For example:

  • Cursor Models — progress bar + percentage used
  • Other Models — progress bar + percentage used
  • Grok Bot — weekly progress bar + percentage used
  • Reset date / billing cycle
  • Remaining included usage

All editable controls, including On-Demand Usage and spend limits, could remain completely hidden or disabled for members when “Only Admins Can Edit Usage Settings” is enabled.

So I agree that the current behavior may be working as designed from a permissions perspective. My suggestion is more specifically a feature / UX improvement:

Please give Team members a read-only Included Usage view with the same quota visibility and progress indicators that admins and personal users already have, without exposing any editable usage settings.

I think this would make the permission model much clearer and would also prevent members from having to ask admins how much quota they have left.