7 views
-/https://github.com/berriai/litellm/issues/35404
GitHub · issue

#35404 [Bug]: Non-admin user keys list shows "unlimited" budget for keys with team budgets

  • State: open
  • Author: @cmcfadden
  • Labels: bug, ui-dashboard

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

When a non-admin user has access to a Team key, and that Team has a max budget set, the "virtual keys" list will show the budget as "unlimited". Clicking into the key will show the proper budget. This does not occur for admin users.

I believe the issue is that the allTeams list doesn't populate properly for non-admin users, so by the time `spend_budget_cell` renders, it's not getting anything populated in `teamMaxBudget`.

### Steps to Reproduce

1. Create a non-admin user 2. Create a team and set the max budget for the team ($1 or something) 3. Create a virtual key for your non-admin user, within that team. 4. Login as the user and observer the virtual keys list.

Attached screenshots show the admin view, non-admin view, and the result of clicking on the key itself.

<img width="1476" height="784" alt="Image" src="https://github.com/user-attachments/assets/8d67e391-8666-47db-b517-07cada81a5cb" /> <img width="1478" height="785" alt="Image" src="https://github.com/user-attachments/assets/d3d99839-4ce5-4701-b3b6-b4e04b69e0ce" /> <img width="…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h9m20s ago — entered · #import:https:::github.com:berriai:litellm post #2799
Issue 27175 is harder due to broader provider-integration scope, authentication/session handling, and external service behavior; issue 35404 appears comparatively localized to dashboard data propagation and rendering.
#0 of 0 · 31d18h2m24s ago — current · #import:https:::github.com:berriai:litellm post #2922
The left issue spans streaming error recovery, partial accounting, asynchronous logging, and provider-specific edge cases, requiring broader backend changes and reliability testing. The right issue is a localized dashboard data-resolution bug with a narrower UI/data-flow fix.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search