Adjust a workspace's AI credits
What this achieves
Section titled “What this achieves”AI features draw on a workspace’s credit balance, which comes from its plan each month and from any top-up bought on top. This is where credits are added to a workspace or a balance is corrected, and every movement is recorded.
Required role: Humavera platform staff.
- Go to Platform → Tenants and open the workspace.
- Open the Credits tab.
- Read Included, Top-up, and Total available for where the balance stands.
- To grant credits, enter the number under Add top-up credits, enter a Reason, and select Add.
- To correct a balance, enter a signed figure under Manual adjustment, choose the pool, enter a Reason, and select Apply.
- Read Credit transactions to confirm the movement was recorded.
The two pools behave differently
Section titled “The two pools behave differently”| Option | Description |
|---|---|
| Included | The plan’s monthly allowance. It resets each cycle and unused credits do not carry over. |
| Top-up | Bought or granted separately. It does not expire and survives a plan change. |
| Total available | The two added together, which is what the workspace can actually spend. |
Example: a workspace granted top-up credits as a goodwill gesture still has them next month, after the included pool has reset.
A reason is required, not optional
Section titled “A reason is required, not optional”Neither the top-up nor the adjustment will submit without a reason. That is deliberate. Credit movements made from the platform side are the ones nobody in the customer’s workspace can explain, so the reason you type is the only account of why the number changed.
Example: recording a correction as a refund for a failed run tells the next person exactly what happened. A blank or vague reason turns a routine correction into a query later.
Manual adjustments take a sign
Section titled “Manual adjustments take a sign”Manual adjustment accepts a positive or negative figure and applies it to the pool you choose. A negative adjustment reduces a pool, and a pool cannot go below zero.
Use a top-up for granting credits and an adjustment for correcting a balance that is wrong. They land in different places and read differently in the record.
Reading the record
Section titled “Reading the record”Credit transactions lists every movement against the workspace with its amount and time, whether the credits arrived from a monthly reset, were consumed by use, were added as a top-up, moved because the plan changed, or were adjusted or refunded by hand. Additions and deductions are distinguished, so a balance can be reconstructed rather than guessed at.
Credits can also be reached from the workspace list without opening the record, using Manage credits on the row’s actions menu.
What happens next
Section titled “What happens next”The new balance is live for the customer immediately. Inside their workspace, credits also have to be allocated to individual people before they can be used — a workspace with a healthy pool and no allocations still has nobody able to use an AI feature.
Related
Section titled “Related”© 2025-2026 Humavera Documentation - BPilot Ltd. All Rights Reserved