{{define "admin_quotas"}}
What each organization, team and project may use · spend over the last {{.Since}}
{{.Error}}
{{end}} {{if .Message}}{{.Message}}
{{end}} {{if .Rows}} {{/* The tree is the interface. A quota belongs to a branch, so the form to set one opens on that branch rather than asking somebody to name it again in a box at the bottom. */}}| Where | RPM | TPM | Budget | Spent | Used | |
|---|---|---|---|---|---|---|
| {{if eq .Indent 0}}{{.Path}}{{else}}{{.Path}}{{end}} {{.Scope}} | {{if .RPM}}{{.RPM}}{{else}}—{{end}} | {{if .TPM}}{{.TPM}}{{else}}—{{end}} | {{if .Budget}}{{.Budget}}{{if .Period}}/{{.Period}}{{end}}{{else}}—{{end}} | {{.Spend}} | {{if .HasPct}}{{.Percent}}%{{else}}—{{end}} | {{if .Editing}}close {{else}}{{if .HasAny}}change{{else}}set quota{{end}}{{end}} |
| written here, but {{.Shadowed}} | ||||||
only: {{.Models}} | ||||||
Nothing to give a quota to yet. Make an organization on the accounts page first.
{{end}}Limits compose downward by taking the most restrictive value, so a team cannot raise what its organization set and a project cannot raise its team's. Only an organization's own limit is bounded by nothing. Model lists intersect rather than add: a project cannot allow a model its team withheld.
Still not here, deliberately: per-key limits. A key is issued by
the person who owns it and bounded by the project it belongs to, and letting an
admin session reach individual keys would put every caller's throughput one
click away — llmgw keys limits --scope key for that.