Contracts & capacity
Contracts & capacity define what your organization is entitled to on X4RGE — plan type, monthly included allowance, product seats, and usage caps. Think of it as your plan ceiling: everything your admins configure in the dashboard stays at or below this entitlement.
Operators set contracts in the Console. You see the result on Usage as the Included bucket and in organization settings. You typically do not edit the contract yourself — but you do manage budgets and models inside it.
What this page is for
Contract = what your plan includes (set by X4RGE / your agreement). Budget = how strictly your admin caps spend inside that allowance on Usage.
Why contracts matter
When a customer upgrades, renews, or starts a trial, operators update the contract — then org admins allocate that entitlement internally with budget policies.
How contracts show up for you
If you are an organization admin, you interact with contracts indirectly through Usage and settings — not through Console.
Refresh Usage after a known plan change. If Included still does not match your agreement, contact your X4RGE operator or Help & support with your org name and expected allowance — see Governance for audit context.
In practice
Pick the row that matches your role and goal.
What's in a contract
A contract is the commercial snapshot for your organization — not something you edit in the dashboard, but the fields below explain what you see reflected in product.
The monthly allowance powers the Included bucket on Usage. Org admins set budgets at or below that amount — never above.
Capacity vs org budget
Two layers control spend. Customers feel both — but only admins control the second layer.
Think of the contract as your plan allowance. Budgets are house rules your admin sets inside that allowance — you can be stricter than the plan, not more generous without a contract change.
For organization admins
You do not edit contracts in Console. You do use what they enable every day:
Check Included on Usage
Open Usage. Included reflects your plan allowance; On-demand is beyond that.
Set an internal budget
In Settings or Usage, set a monthly cap at or below your allowance if you want stricter control.
Curate models
Model control only offers models your plan includes — disabling costly models saves allowance without changing the contract.
If numbers look wrong
Refresh Usage after a known plan change. If Included still doesn't match your agreement, contact your X4RGE operator or support with org name and expected allowance.
Budget block — your admin may raise the internal cap on Usage if still under Included. Plan block — entitlement must change in Console; contact support or your account contact.
For platform operators
These steps are for Console users when agreements change — upgrades, renewals, trials, or corrections.
Operators update capacity when agreements change — mid-contract upgrades, trial extensions, or enterprise true-ups.
Open the client
In Console, go to Clients → select the organization → Contract.
Review current usage
Compare the org's Usage for the month against existing limits. Note whether this is upgrade, downgrade, or correction.
Apply the update
Set plan type, support tier, dates, allowance, and limits. Enter a clear reason (for example, "Q3 enterprise renewal — increased allowance").
Confirm with the customer
Ask the org admin to refresh Usage and verify Included and license counts updated.
Align with finance
Match the Console change to your CRM or billing record so support and finance stay in sync.
Capacity changes take effect immediately for the organization and show in their usage view. Always record a reason — it appears in the audit log.
Trial to enterprise
A typical customer journey from pilot to paid plan — operators set entitlement at each phase; customer admins roll out GitHub, budgets, and models inside the new ceiling.
Lowering monthly allowance below what the org already consumed this month does not cancel runs in progress. Coordinate with the customer before downgrading mid-cycle.