9 views
-/https://github.com/berriai/litellm/issues/32451
GitHub · issue

#32451 [Feature]: Control which Usage view dropdown options are visible to internal users

  • State: open
  • Author: @emil-stromsvag-nrk
  • Labels: enhancement, proxy

### Check for existing issues

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

### The Feature

Add an admin setting under **Settings → Admin Settings → UI Settings** that allows proxy admins to configure which usage view options are visible to non-admin internal users in the Usage page dropdown.

Currently, the Usage page dropdown shows these options to `internal_user` / `internal_user_viewer` roles:

- **Your Usage** (`global` with `showForNonAdmin` label) - **Your Organization Usage** (`organization` with `showForNonAdmin` label) - **Team Usage** (`team`) - **Tag Usage** (`tag` — has `adminOnly: true` but is overridden by a `canViewTagUsage` check that includes all `internalUserRoles`)

The proposal is to add a configuration — both in the Admin UI (alongside the existing "Configure Page Visibility" panel) and via the `PATCH /ui_settings/update` API — that lets admins select which of these dropdown options internal users can see.

**Admin UI:** A new section in UI Settings (e.g., "Configure Usage View Visibility") with checkboxes for each usage view option, similar to how page visibility is already configured.

**API:** Extend the existing…

GitHub resolver

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

Refresh page
vote history (3 events)
#0 of 0 · 31d18h38m30s ago — entered · #import:https:::github.com:berriai:litellm post #2243
#31441 is harder because it requires diagnosing and safely changing cross-request cached state across accounting, limits, and regional routing, with concurrency, backward-compatibility, and regression-test risks. #32451 is primarily an additive UI/API configuration change following existing visibility-setting patterns.
The left issue is harder because it spans Vertex pass-through routing, request-body model resolution, persisted origin context across asynchronous follow-up calls, configuration gating, and multi-project credential behavior. The right issue is mainly a bounded admin UI and settings/API extension using existing visibility patterns.
#0 of 0 · 31d17h57m45s ago — current · #import:https:::github.com:berriai:litellm post #2914
The right issue is harder because it requires coordinated configuration modeling, API and persistence changes, admin-interface work, authorization behavior, and cross-role testing. The left issue is narrower, centered on defensive client-side aggregation and correct handling of paginated usage data.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search