From f70b7575d2a4295cd656378192383c3fe985cf57 Mon Sep 17 00:00:00 2001 From: Ishaan Jaff Date: Thu, 29 Aug 2024 21:00:10 -0700 Subject: [PATCH] update docs --- docs/my-website/docs/proxy/tag_routing.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/my-website/docs/proxy/tag_routing.md b/docs/my-website/docs/proxy/tag_routing.md index e63a35deee7..603c47fad18 100644 --- a/docs/my-website/docs/proxy/tag_routing.md +++ b/docs/my-website/docs/proxy/tag_routing.md @@ -3,7 +3,7 @@ Route requests based on tags. This is useful for - Implementing free / paid tiers for users -- Controlling model access per team, example Team A can access gpt-4 deployment A, Team B can access gpt-4 deployment B +- Controlling model access per team, example Team A can access gpt-4 deployment A, Team B can access gpt-4 deployment B (LLM Access Control For Teams ) ## Quick Start @@ -138,8 +138,7 @@ Response ## ✨ Team based tag routing (Enterprise) -LiteLLM Proxy supports team-based tag routing, allowing you to associate specific tags with teams and route requests accordingly. Example **Team A can access gpt-4 deployment A, Team B can access gpt-4 deployment B** - +LiteLLM Proxy supports team-based tag routing, allowing you to associate specific tags with teams and route requests accordingly. Example **Team A can access gpt-4 deployment A, Team B can access gpt-4 deployment B** (LLM Access Control For Teams) :::info