Site administration
Give one account higher limits
One user or organization needs more CI containers or a higher AI spend cap than the rest of the site, for example your own organization. An account override gives it its own limits.
2 min read
You need to be a site admin.
1. Open the Account overrides card
Open Limits, then go to the Account overrides card.
2. Type the account and its limits
- In Account, type the name of the user or the organization.
- Type the new limits. Leave a field empty to use the value of the site.
| Field | Range | What it replaces, for this account |
|---|---|---|
| CI containers | 1 to 1,000 | Both the limit per account and the limit per repository, for the repositories of this account. |
| Monthly AI cap | 1 to 100,000 dollars | The AI spend cap of the site. |
CI and AI lists the values of the site.
3. Save
Click Save.
Done
The table of the card shows the account, its CI containers and its monthly AI cap. The account uses its new limits within about a minute.
An override can also be lower than the value of the site. Two settings can still lower an override:
- The CI settings of a repository can set fewer containers for that repository.
- The owners of an organization can set a lower cap in its factory settings.
Change or remove an override
To change an override, save the account again with the new values. To go back to the limits of the site, click Remove in the row of the account, then click Remove limits.
While billing is on
When a site admin turns on billing, the plan of each account sets its limits. An override still holds over the plan:
- CI containers wins over the containers of the plan, for the account and for each of its repositories.
- Monthly AI cap still caps what Source pays for the models of the account. It holds also when the plan, the credits or the overage leave more.