β¨ [Beta] Project Management UI
This is an Enterprise feature. Enterprise Pricing
Manage projects directly from the LiteLLM Admin UI. Projects sit between teams and keys in your organizational hierarchy, enabling fine-grained access control and budget management for specific use cases or applications.
Project Management is a beta feature. The API and UI are subject to change. For the full API documentation, see Project Management.
Overviewβ
Projects enable you to:
- Organize API keys by use case or application
- Set project-level budgets and rate limits
- Track spend and usage at the project level
- Control which models each project can access
- Maintain clear separation between different applications or teams
Hierarchy: Organizations > Teams > Projects > Keys
For detailed information about the project API and configuration, see Project Management.
Prerequisitesβ
- Admin or Team Admin access
- At least one team created (projects belong to teams)
- The LiteLLM Admin UI running locally or remote
Enable Projects in UI Settingsβ
Before you can create projects, you need to enable the Projects feature in the Admin UI settings.
Step 1: Access Admin Settingsβ
Navigate to the Admin UI (e.g., http://localhost:4000/ui/?login=success).
Step 2: Open Settings Menuβ
Click the "New" button in the top navigation.
Step 3: Navigate to Admin Settingsβ
Click "Admin Settings".
Step 4: Open UI Settingsβ
Click "UI Settings New".
Step 5: Enable Projects Featureβ
Click the toggle to enable the Projects feature.
Once enabled, the Projects section will appear in your Admin UI navigation, and you'll be able to create and manage projects.
Create and Manage Projectsβ
After enabling the Projects feature, you can create projects from the Projects page.
Step 1: Navigate to Projectsβ
Click "Projects New" in the sidebar.
Step 2: Create a New Projectβ
Click "Create Project".
Step 3: Enter Project Nameβ
Click the "Project Name" field and enter a name for your project.
Step 4: Select a Teamβ
Choose which team this project belongs to. Projects are scoped to teams, so you can only access models and features available to that team.
Step 5: Configure Model Accessβ
Select which models this project has access to. Available models are scoped to the team's allowed models.
Step 6: Create Projectβ
Click "Create Project" to save your project.
Use Casesβ
Key Organization Within Teamsβ
Organize API keys within a team by use case or application. Group related keys together in projects so you can manage budgets, model access, and permissions as a unit instead of individually.
Cost Allocationβ
Assign projects to different cost centers or teams. Track spend per project and allocate costs back to the responsible team or business unit.
Feature Rolloutβ
Create a dedicated project for new features or experimental use cases. Control which models are available and set conservative rate limits during testing.
Customer Segmentationβ
If you're a platform, create projects for different customer segments or use cases. Control resource allocation independently for each segment.
Next Stepsβ
After creating a project:
- Generate API Keys β Create API keys scoped to your project for application use
- Set Budgets β Configure project-level budget limits via the Project Management API
- Track Spend β View project-level spend in the Usage dashboard
- Manage Access β Use Access Groups to control model and MCP server access
Related Documentationβ
- Project Management API β Full API reference for projects
- Access Groups β Define reusable access controls for models, MCP servers, and agents
- Virtual Keys β Create and manage API keys scoped to projects
- Role-based Access Control β Organizations, teams, and user roles
- Spend Logs β Track detailed request-level costs and usage