Management Permissions Reference
This reference describes the new dashboard’s customer-facing management capabilities. Native LiteLLM endpoint availability is separate from permission to use it; a route appearing in an upstream schema is not a grant of access.
Current dashboard capabilities
| Task | Page | Scope and limits |
|---|---|---|
| Create an API key | API Keys | Self-owned key in the selected team; model and spending limits apply. |
| Rename/block/unblock/delete a key | API Keys | Controls appear only when the account has the corresponding permission. |
| View balance and activity | Overview / Usage | Team balance; activity visibility follows account permissions. |
| Inspect a request | Logs → View details | Recorded request metadata, tokens, and spend; no prompt/response content or raw usage-object viewer. |
| Invite/remove members | Members | Team Admin or platform administrator, within the selected team; protected accounts are excluded. |
| Promote/demote a Team Admin | Members | Dashboard delegation only; preserves a final Team Admin and does not change global/native roles. |
| Set a member budget | Members → Set budget | Ordinary members; shared across their keys. Team Admins cannot change their own or another admin’s cap. |
| Change profile/password | Settings | Signed-in account; password change requires the current password. |
| Add credit | Overview / Usage → Top up | Payment flow using the current account email; contact support for ambiguous destinations. |
Native management APIs
Paths such as /key/generate, /key/update, /team/info, /team/member_add, and /team/member_update belong to the underlying management API. These names are not a promise that a customer key can call them. Access can depend on the credential, route restrictions, team membership, native role, and supported features.
Dashboard Team Admin delegation does not automatically authorize these routes. An ordinary key’s model permission such as all-team-models is an inference selection, not a management permission. Platform-wide model, user, organization, credential, and spend-reset operations are not customer dashboard actions.
For a separately approved automation integration, obtain the exact route contract from the platform administrator. See Team Management & Automation and Members & Budgets for the supported customer workflows. Never infer support from an old blanket “Team Admin Allowed” endpoint list.