← Back to Documentation
Access & Controls
Rate Limits and Quotas
Set usage limits that protect shared infrastructure and keep AI spend predictable.
Key Steps
- Use quotas to guide normal employee behavior before rate limits become a support issue.
- Align limits with plan allowances, provider budgets, and internal policy.
- Review quota changes alongside usage and cost reports.
Article Scope
This guide focuses on the operational steps needed to run Orchestris with team access, provider control, and predictable usage.
Visual Reference
How limits work
- Plan limits define the broad entitlement for a license.
- Overrides can tune specific licenses, teams, or users.
- Rate limits protect the server and providers from bursts that exceed expected traffic.
Setting practical quotas
- Start with the expected daily workflow volume for each user group.
- Give administrators a process for approving temporary increases.
- Use reports to distinguish normal growth from misuse or automation loops.
Handling 429 responses
- Clients and automation should respect retry hints.
- Investigate repeated 429s for a single user or integration.
- Raise quotas only after confirming provider spend and infrastructure capacity.
Related Topics
Access & Controls
User Management
Invite employees, manage account status, and keep access aligned with business roles.
Access & Controls
Access Control
Use roles, quotas, and model availability to keep AI access appropriate for each team.
Access & Controls
Team Sign-In Planning
Plan identity requirements for private deployments and future enterprise sign-in work.