Organization coverage policies
Manage coverage in Credits & Usage (/credits) in Backoffice. The page is
for organization administrators. It shows what the organization has left, who
has used its credits this month, and the policy that decides how they are
shared. Platform administrators can also configure an organization's policy.
For the extension, Managed Only covers active organization members; Public also allows coverage on the policy's permitted domains. The Covers Extension switch controls extension sponsorship.
Widget turns always charge the embed's organization. The coverage type and Covers Widget switch do not disable access to the widget. Control admission in the host application's sign-in system. Restrict widget keys to the intended domains and deactivate a key to stop that embed.
Limit individual consumption
Set Per-User Credit Cap in Credits & Usage to a finite allowance. The cap applies to recorded organization-paid consumption since the start of the calendar month, or since an administrator last restored that person's allowance (see below), including the linked user's federated widget turns. Once the cap is reached, the next turn is refused. A widget identity without a linked Appilot user cannot use an allowance that requires this per-user cap.
The cap is checked before a turn. It does not reserve the maximum possible cost of a running turn, so concurrent or long turns can exceed the threshold. Use a finite organization credit balance and a low widget-key request rate alongside it. A failure to check the allowance refuses the turn.
The Per-Session Limit field is stored but is not currently enforced. Do not rely on it to limit spending. Every widget conversation requires an identified user; there are no anonymous widget conversations.
See who has reached the cap
Organization allowance at the top of the page shows the credits the organization has left out of what it was granted, and how many it has used.
Usage by person lists every member of the organization, plus anyone who spent its credits this month without being a member. A signed-in widget visitor whose Appilot account does not belong to the organization is the usual case, and the table marks them Not a member. People who have reached the cap come first, then everyone else by how much they have used.
Each row shows the credits the person has used since the first of the month,
or since their allowance was last restored. When a cap is set, the row shows
that figure against the cap (for example 3.2 / 5) and says Limit reached
once the person can no longer start a turn on the organization's credits.
Without a cap the table shows usage only.
Restore one person's allowance
Restore allowance gives one person their monthly allowance back without raising the cap for everybody. It appears when a cap is set and the person has used something this month. After you confirm, the person's count starts again from zero at that moment, and the row shows Allowance restored on the date. The restore changes only the count the cap reads. Credits the person already used stay spent, so the organization's balance and its usage history do not change.
A restore lasts until the end of the calendar month. On the first of the next month everyone starts from zero anyway, and the restore date no longer shows.
Restore an allowance when one person needs more this month, such as a presenter before a demonstration. When several people keep reaching the cap, raise Per-User Credit Cap instead. Saving the policy updates the table, since the cap decides who has reached it.
Closed beta
An active plan and credit allowance are still required during closed beta. The platform team assigns the allowance; payment checkout is unavailable. When credit runs out, the panel directs the user to support. Closed-beta mode does not bypass credit checks.
For invited demonstrations, restrict access in the host app before issuing federated identities. A fixed list of demo personas by itself does not stop public visitors from sharing those personas and consuming their allowance.