Check for existing issues

• I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

An org_admin user navigating to the Usage tab and selecting "Your Organization Usage" sees completely empty data: Total Spend $0.00, Total Requests 0, and all charts show "No data" -- despite active traffic on keys associated with that organization.

The root cause is in the UI layer: the Usage page hardcodes an empty organizations array instead of fetching the user's organizations, so the EntityUsage component receives no organization context and cannot populate its filter dropdown or correlate data to named organizations.

The backend endpoints (/organization/daily/activity and /organization/list) correctly handle org_admin authorization and would return proper data if called with the right context.

Root Cause Analysis

The bug: Usage page does not fetch organizations

In ui/litellm-dashboard/src/app/(dashboard)/usage/page.tsx:11:

return <UsagePageView teams={teams ?? []} organizations={[]} />;

The organizations prop is hardcoded as []. The page imports useTeams to fetch teams but does NOT import or use the useOrganizations() hook.

The correct pattern already exists

In ui/litellm-dashboard/src/app/(dashboard)/users/page.tsx:6,16:

import { useOrganizations } from "@/app/(dashboard)/hooks/organizations/useOrganizations";
// ...
const { data: organizations, isLoading: isOrgsLoading } = useOrganizations();

The users page correctly fetches organizations and passes them downstream. The Usage page skips this entirely.

Downstream chain reaction

Step 1 -- UsagePageView.tsx:836-844 receives organizations=[] and maps it to entityList:

{usageView === "organization" && (
  <EntityUsage
    entityType="organization"
    entityList={
      organizations?.map((organization) => ({
        label: organization.organization_alias,
        value: organization.organization_id,
      })) || null
    }

Since organizations=[], this produces entityList=[] (empty array, not null).

Step 2 -- EntityUsage.tsx receives entityList=[]:

• The filter dropdown check entityList !== null && entityList.length > 0 evaluates to false -- filters are hidden
• selectedTags remains empty, so entityFilterArg = null
• The API call fires with organizationIds=null

Step 3 -- networking.tsx:1952-1969 sends request to /organization/daily/activity with no organization_ids parameter.

Step 4 -- Backend organization_endpoints.py:319-343 correctly defaults to org_admin's organizations when org_ids_list is None:

if not _user_has_admin_view(user_api_key_dict):
    memberships = await prisma_client.db.litellm_organizationmembership.find_many(
        where={"user_id": user_api_key_dict.user_id}
    )
    admin_org_ids = [
        m.organization_id for m in memberships
        if m.user_role == LitellmUserRoles.ORG_ADMIN.value
    ]
    if org_ids_list is None:
        org_ids_list = admin_org_ids  # Defaults correctly

The backend returns data for the org_admin's organizations, but the UI has no organization names to display in filters, no way for the user to select/deselect orgs, and the overall experience appears broken.

Backend verification: both endpoints work for org_admin

1. /organization/list (organization_endpoints.py:661-710) -- for non-proxy-admin users, it queries LiteLLM_OrganizationMembership and returns only orgs where the user has membership. No proxy_admin gate.

2. /organization/daily/activity (organization_endpoints.py:282-371) -- for non-proxy-admin users, it defaults to orgs where user is org_admin. Authorization is correct.

Expected behavior

• org_admin users should see a populated organization filter dropdown on the Usage tab
• Aggregated spend data (Total Spend, Total Requests, Successful/Failed Requests) should display for their organization(s)
• Daily Spend chart and "Spend Per Organization" table should show data corresponding to traffic on keys in their organization

Actual behavior

• The "Your Organization Usage" view shows $0.00 / 0 / 0 / 0 for all metrics
• Charts display "No data"
• Organization filter dropdown is empty/hidden -- user cannot select which organizations to view
• No error messages are shown (the call may technically return data but the UI cannot display it meaningfully)

Steps to Reproduce

1. As proxy_admin, create an organization (e.g., acme-corp) via /organization/new
2. Create a user with global role internal_user (the default)
3. Add the user as org_admin for acme-corp via /organization/member_add
4. Create API keys with organization_id set to acme-corp's ID
5. Generate traffic using those keys (make some LLM calls)
6. Wait for spend to be recorded in LiteLLM_DailyOrganizationSpend table
7. Log into the Admin UI as the org_admin user
8. Navigate to Usage tab, observe "Your Organization Usage" is selected
9. Observe: All metrics show $0.00 / 0, charts show "No data", no organization filter dropdown visible

Suggested fix

Fix: Use useOrganizations() hook in the Usage page

Update ui/litellm-dashboard/src/app/(dashboard)/usage/page.tsx to fetch organizations, mirroring the pattern already used in users/page.tsx:

"use client";

import UsagePageView from "@/components/UsagePage/components/UsagePageView";
import useAuthorized from "@/app/(dashboard)/hooks/useAuthorized";
import useTeams from "@/app/(dashboard)/hooks/useTeams";
import { useOrganizations } from "@/app/(dashboard)/hooks/organizations/useOrganizations";

const UsagePage = () => {
  const { accessToken, userRole, userId, premiumUser } = useAuthorized();
  const { teams } = useTeams();
  const { data: organizations } = useOrganizations();

  return <UsagePageView teams={teams ?? []} organizations={organizations ?? []} />;
};

export default UsagePage;

Why this works:

• useOrganizations() calls organizationListCall(accessToken) which hits /organization/list
• /organization/list already correctly returns only the user's organizations for non-proxy-admin users
• UsagePageView will then pass a populated entityList to EntityUsage
• The organization filter dropdown will appear, allowing org selection
• The API call to /organization/daily/activity will work as already implemented

No backend changes needed -- both /organization/list and /organization/daily/activity already handle org_admin authorization correctly.

Related code locations

Relevant log output

What part of LiteLLM is this about?

UI Dashboard

What LiteLLM version are you on ?

v1.82.3

Twitter / LinkedIn details

No response