Tenant tokens

Tenant admin

The tenant holds a token balance. Users and projects hold their own balances, allocated out of it. Jobs spend from a user or a project, never from the tenant directly.

The tenant balance

Shown at the top of the page. Adding to it is a superadmin matter - your tenant was given a balance, or a subscription tops it up. What you control is how it is distributed.

Allocating to users

Set any user’s balance from here, or from the user’s own entry on the Users page. The user sees the change as a Credit in their transaction history, attributed to the tenant administrator.

Allocating to projects

The same, for projects. A project balance is the right tool when several people work on one thing and you want the cost attributed to the work.

Allocate a little, often

There is no overdraft: a user whose balance will not cover a job’s estimate simply cannot submit it. Small regular allocations - by hand or through a recurring task - keep that from becoming a daily interruption while still bounding the spend.

What spends them

Charge	Falls on
Job start cost	The user, or the project if one is selected
Runtime per minute	Same
Storage per terabyte-hour	The owner of the bucket

Runtime is scaled by resources held and by the queue’s own cost factors, so the same job on two queues does not cost the same. See Queues.