docs: document default_team_params in config reference

[ryan-crabbe-berri]

Summary

• Add default_team_params to the litellm_settings reference table in config_settings.md with all sub-fields documented
• Update self_serve.md and msft_sso.md config examples to include team_member_permissions, tpm_limit, and rpm_limit
• Fix misleading comment that implied default_team_params only applies to SSO auto-created teams — it applies to all /team/new calls

Test plan

• Verify docs render correctly on local Docusaurus dev server

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Apr 2, 2026 11:02pm

[greptile-apps]

Greptile Summary

This is a pure documentation PR that adds default_team_params to the litellm_settings config reference table and updates YAML examples in self_serve.md and msft_sso.md with the full set of supported sub-fields (tpm_limit, rpm_limit, team_member_permissions). It also corrects the previously misleading comment that implied the setting only applied to SSO auto-created teams — it applies to all /team/new calls, with the exception of models, which is correctly documented as SSO-only.

The documentation changes are accurate and consistent with the implementation:

• max_budget, budget_duration, tpm_limit, rpm_limit, and team_member_permissions are applied via the explicit loop in team_endpoints.py (lines 862–868) for all /team/new calls
• models is applied only through the _cast_and_deepcopy_litellm_default_team_params SSO path in ui_sso.py, which is correctly annotated in every updated example
• The KeyManagementRoutes enum confirms that /team/daily/activity and /key/generate are valid route strings for team_member_permissions
• The budget_duration example value "30d" is a valid format per the proxy _types.py docstring

The previous Greptile finding about models being incorrectly documented as applying to all /team/new calls has been addressed in this PR.

Confidence Score: 5/5

Documentation-only PR; all sub-field descriptions and applicability scopes have been verified against the implementation and are accurate.

No code changes are introduced. All documented sub-fields, their types, and their scope (SSO-only vs. all /team/new calls) are consistent with the source code in team_endpoints.py and ui_sso.py. The prior models-applicability concern raised in the previous Greptile review has been addressed explicitly.

No files require special attention.

Important Files Changed

Filename	Overview
docs/my-website/docs/proxy/config_settings.md	Adds a new default_team_params row to the litellm_settings reference table; sub-fields and their applicability scope are accurately described and match the source code in team_endpoints.py and ui_sso.py.
docs/my-website/docs/proxy/self_serve.md	Updates two YAML code examples to include tpm_limit, rpm_limit, and team_member_permissions; also corrects the misleading comment that implied default_team_params was SSO-only. Minor inconsistency: the second comprehensive config block omits inline comments and the second permission route present in the first example.
docs/my-website/docs/tutorials/msft_sso.md	Updates the Microsoft SSO config example to include team_member_permissions, aligning it with the other updated examples. Changes are accurate and non-breaking.

_{Reviews (2): Last reviewed commit: "docs: clarify that models sub-field only..." | Re-trigger Greptile}

[greptile-apps]

models sub-field does not apply to all /team/new calls

The description states that default_team_params "Default parameters applied to every new team created via /team/new", and lists models as a sub-field. However, in litellm/proxy/management_endpoints/team_endpoints.py (lines 862–868), the loop that backfills defaults only iterates over max_budget, budget_duration, tpm_limit, rpm_limit, and team_member_permissions — models is deliberately excluded:

for field in (
    "max_budget",
    "budget_duration",
    "tpm_limit",
    "rpm_limit",
    "team_member_permissions",
):

models is applied for SSO-created teams because ui_sso.py copies all DefaultTeamSSOParams fields into the NewTeamRequest before calling new_team(). But a user making a direct POST /team/new request without specifying models will not have models populated from default_team_params.

The documentation should either clarify that the models field only takes effect for SSO auto-created teams, or "models" should be added to the loop in team_endpoints.py to make the behaviour consistent with the documented claim.

The same note should be added to self_serve.md (line ~364) and msft_sso.md (line ~134) wherever models appears under default_team_params.