### Check for existing issues

- [x] 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

**Workaroun…