Allocate AI credits

What this achieves

AI credits are held as a company pool and given to individual employees as a personal allowance. Allocation is not optional housekeeping — an employee with no allocation cannot use Humavera’s AI features.

Required role: Administrator.

Steps

Go to Settings → AI Credit Allocation.
Under Allocate to employee, choose the employee.
Enter the number of Credits.
Select Allocate.
Select Save.

No allocation means no access

This is the rule to understand before anything else on the page. Unallocated employees cannot use AI features. Access follows allocation, so a person with nothing allocated does not fall back on a shared pool — they have no AI at all.

Example: if Priya Raman is allocated credits at HC Corp UK Ltd and James Whitfield is not, Priya can ask Vera and James cannot. Nothing else distinguishes them.

Decide who needs AI before distributing, and expect to be asked by anyone who does not have it.

What the figures mean

Option	Description
Allocatable pool	The total available to distribute — included credits plus any top-up.
Allocated	How much of the pool is committed to employees.
Unallocated	What is left to give out.
Used	What an employee has consumed from their allowance.
Remaining	What an employee has left.

The pool is a hard cap

The sum of all allocations cannot exceed the allocatable pool. You cannot promise more than you hold, so allocating generously to early recipients leaves nothing for the rest.

Example: distributing most of HC Corp UK Ltd’s pool across Engineering leaves little for Finance and People, and there is no overdraft.

Hold some back rather than distributing everything at once. Someone will need credits you did not anticipate.

Resets, and what does not reset

Allowances reset each billing cycle, and usage resets to zero with them. Top-up credits never expire, unlike included credits, which do reset.

That distinction matters when planning. Included credits are use-them-or-lose-them within the cycle; a top-up carries forward.

Example: an HC Corp UK Ltd employee who uses none of their allowance this cycle does not accumulate a larger allowance next cycle — it resets.

When credits run low

Humavera warns when the pool is running low, showing the percentage remaining, and again when included credits are exhausted, showing when they reset. Both are workspace-level signals rather than per-employee ones.

What happens next

Allocated employees can use AI features up to their allowance, and their usage appears against them here. Where consumption is uneven, reallocating between people is the lever — the pool is fixed within a cycle, so moving credits is how you respond to real demand. What each AI feature costs and how the pool is sized are questions for your plan rather than this screen.