Credits
Balance, runway, where they went, and per-member limits.
Credits in the console.
This section applies only if your organisation runs on credits. If you use your own provider keys, the page tells you so and your providers bill you directly, and everything here is then irrelevant. See How billing works.
Balance and runway
Available balance, in credits, with an estimate of how long it lasts at recent usage ("about 23 days left"). Too little recent usage and it says so rather than guessing.
Runway is the number to watch. A balance means nothing without a rate, and the whole point of the estimate is to give you notice before a Friday afternoon.
Expiring soon lists grants with an expiry date. Credits that expire unused are worth spotting a month out, not a day out.
Topping up is not self-service: contact your Asteria Cloud representative.
Overdrawn
If usage settles after the balance ran out, you go negative and the page explains that a top-up clears it. Work is not silently lost.
Where your credits went
A breakdown over a recent window by activity: chat, documents, research, indexing documents, web search, images, evaluations, workflows.
Useful for the questions you will actually have. Indexing spiking means somebody built a large collection, probably with vision parsing on. Evaluations climbing means somebody is running datasets frequently, which is good practice and does have a bill. Workflows growing without anyone mentioning it means a schedule is running that nobody is watching.
Some usage cannot be attributed to an activity and appears as Other activity. That is settled against your provider's own total rather than broken out, so it is a real cost with a coarse label rather than a rounding error.
Per-member limits
Cap how much of the shared pool any one member can use in a calendar month.
A limit is a ceiling on that person's usage, not a separate balance. The pool stays shared. Giving everyone a limit does not carve the balance into portions, and the sum of limits can happily exceed what you hold.
Set a default for everyone, and override individuals. Leave it empty for no limit.
A member at their limit is paused until next month and told so, with a note that an administrator can raise it. Over but not blocked, they are told nothing is blocked yet.
The default is worth setting even generously. It is not about rationing, it is about bounding the accident: one runaway workflow or one enormous evaluation sweep can otherwise spend a month's credits in an afternoon, and a limit turns that into one person's problem for one month.
Enforcement
You may see a note that credit usage is being recorded but not enforced: nothing is blocked, and limits are tracked without being applied.
Worth knowing which mode you are in before relying on a limit to stop anything.