litellm - 💡(How to fix) Fix [Bug]: UI forces team selection for personal keys even when user has model access [1 comments, 2 participants]

Check for existing issues

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

What happened?

In LiteLLM v1.83.14-stable.patch.2, the UI incorrectly forces users to select a team when creating virtual keys, even when:

• User has Internal User role
• User has models directly assigned
• User is a member of teams with model access
• API endpoint /key/generate works correctly without team_id

The error message shown: "Please select a team to continue configuring your Virtual Key. If you do not see any teams, please contact your Proxy Admin to either provide you with access to models or to add you to a team."

Expected Behavior Internal users with model access should be able to create personal keys (Default Team) without being forced to select a specific team.

Actual Behavior UI blocks key creation with team selection requirement, but API works fine.

Environment

• LiteLLM Version: v1.83.14-stable.patch.2
• User Role: Internal User (Create/Delete/View)
• Models assigned to user: Yes (all proxy models)
• Team membership: Yes
• Config: No no-default-models restriction, no key_generation_settings blocking personal keys

Workaround Use API directly:

curl -X POST 'http://proxy:4000/key/generate' \
-H 'Authorization: Bearer <session-token>' \
-H 'Content-Type: application/json' \
-d '{"models": ["gpt-4"], "user_id": "user-id"}'

Steps to Reproduce

1. Assign Internal User (Create/Delete/View) role to a user
2. Assign models directly to the user
3. Add user to a team with models
4. Login as that user
5. Go to UI → Keys → Generate Key
6. Observe forced team selection requirement

Relevant log output

What part of LiteLLM is this about?

UI Dashboard

What LiteLLM version are you on ?

v1.83.14-stable.patch.2

Twitter / LinkedIn details

No response