SubLaneSubLane

Resource allowances

Find and set share, priced-amount, or token limits in a workspace.

Resource allowances are optional. If members only need access to a subscription, grant them a resource group in Members and stop there. Add an allowance when you need to limit how much each person may use from a dedicated pool.

Where to find it

Select the workspace in the switcher at the top of the left sidebar. Then open Administration → Resource allowances → Add resource allowance. The four choices in the form are By share, By amount, By tokens, and By time window.

If Add resource allowance is disabled, first make sure the workspace has an enabled, nonempty resource group that does not already have an allowance. The pool's accounts must not be shared with another pool before you save an allowance.

Example token allowance form with synthetic members and limits:

Resource allowance form showing a selected pool, token mode and member allocation

Prepare the pool and members

  1. Connect and verify a subscription under Accounts.
  2. Under Resource groups, create an enabled pool containing that account. For an allowance, remove its accounts from any other pool in this workspace.
  3. Under Members, open each ordinary member's Group access and grant that pool. Owners and administrators already have access to enabled pools. Anyone with access to the pool can receive its allowance.

A newly connected account is unassigned until you add it to a pool. New members receive no automatic pool grant. These steps all take place in the same selected workspace.

Choose one limit

Choice in the formUse it whenWhat is countedReset
By shareDivide a configured total by member percentagesChoose an internal USD or token total; usage follows the selected unitDaily/monthly calendar reset or independent elapsed-duration windows
By amountGive each member an internal USD allowanceInput, cached-input, and output tokens at the saved model pricesChosen daily time or monthly date and time in the instance time zone
By tokensSet a direct token ceilingInput plus output tokens; cached input is not counted twiceChosen daily time or monthly date and time in the instance time zone
By time windowAdd multiple internal USD limits with shared defaults and optional member overridesEach member has a separate ledger; the same priced request counts in every configured windowEach window starts at activation and renews after its elapsed duration

By share has two bases. Token share counts reported input plus output tokens; cached input is not counted twice. Amount share converts those tokens using the saved model prices. Enter a calendar total or select elapsed windows with a total for each, then set the common member percentages. These budgets are internal: a token total is not the subscription's actual capacity, and USD is not an upstream cash balance or customer invoice. Upstream quota can run out first. For token budgets, 1 M means one million tokens.

Create and use an allowance

  1. Click Add resource allowance, name the rule, and select the dedicated pool.
  2. Choose one of the four types. For By share, choose By token share or By amount share, choose a calendar period or up to eight elapsed windows, enter each total budget, and set member percentages. Shared ratio budgets must be positive; blank-as-unlimited applies only to independent window limits. For By time window, add up to eight conditions with a whole number of hours or days and a shared internal USD limit. Select members, then optionally override individual conditions for one member. A blank USD limit means unlimited for that condition. Other types take one direct member limit. Shares may total at most 100%; Split equally can fill them for you. The member list has a Select all members checkbox in every type.
  3. For By amount, By amount share, or By time window, SubLane fills prices automatically from models supported by the selected pool and snapshots them when saving. Models without a current catalog price use a previously saved price when available; otherwise requests to those models are blocked. The administrator sees current price-coverage warnings. Saving fails only when no usable model price remains. Daily/monthly types also choose a reset clock or date and clock.
  4. Choose when the rule starts and save. For a delayed start, review the server-provided time and select Confirm start time. The workspace's administrator can open View usage on the saved rule; members see their own balances under Usage.
  5. Saving automatically links the selected members’ existing non-revoked keys in that pool to the allowance, preserving key values, pause/expiry settings and client configuration. Members outside the allowance lose access through existing keys. Members without a key create one for the allowance. Older unbound keys offer Restore access when the member is eligible; Change group can move a personal key to another authorized group within the same workspace. Scheduled rules still block use until activation.

One pool can have one allowance. Once saved, its account membership stays fixed even while the rule is paused. Pausing a rule blocks new use of that pool; it does not make the pool freely available. Use Edit current members for funded immediate changes without erasing usage. Budget/price edits stay scheduled and retain window boundaries; unit/type/schedule replacements require explicit new-period confirmation. Access/pause changes affect subsequent requests. The edit form previews the effective date calculated from the current schedule before saving; for time-window rules, a long current window can delay an edit by up to its full duration (at most 365 days). A request already in flight may finish above the remaining allowance.

Before the first activation, use the saved initial rule’s full editor to correct recipients and individual limits while retaining its confirmed start time and accounting anchor. For an already scheduled structural replacement, confirm the new period again to edit its target members; ordinary budget/price edits can retain the existing plan without that confirmation.

For share calculations and manual corrections, read the accounting reference.

Allowance threshold notifications

Enabled workspace webhooks also notify when settled member usage reaches 80% and 95% of the configured allowance. Current accounting windows, ratio limits and member overrides are reused; unlimited, disabled or inaccessible allowances are skipped. Pending exposure is not guessed as settled usage.

Each threshold fires once per accounting period, survives restart and rearms on renewal. Member/price edits do not rearm the same period. The additive allowance_low event carries bounded local identifiers in subject and an anchor-origin revision/reset marker in cycle. Observation failure retains existing incidents; reads are bounded to 4,096 threshold hits per workspace. Notifications go to the administrator webhook, not direct member email, and do not change admission or billing.