Skip to content

docs(credits): document expiry, subscriptions, budgets, alerts and the Credits screen - #3457

Open
rahulgupta-02 wants to merge 8 commits into
LambdaTest:testmuComfrom
rahulgupta-02:docs/credits-management-expand
Open

docs(credits): document expiry, subscriptions, budgets, alerts and the Credits screen#3457
rahulgupta-02 wants to merge 8 commits into
LambdaTest:testmuComfrom
rahulgupta-02:docs/credits-management-expand

Conversation

@rahulgupta-02

Copy link
Copy Markdown

Updates Credits Usage & Management.

Why

The page documents per-feature credit rates well, but not how the credit system itself behaves — expiry, plan grants, budgets, what actually blocks usage, or how to read the Credits screen. That is where most credit questions land.

What's added

Section Covers
How credits are charged Metering (quantity × rate), the hold-then-settle lifecycle, and when a run is refused before it starts
Ways to get credits Dated batches, buying top-ups, requesting credits
When credits expire Per credit type, burn order (soonest-expiring first), and what a cancellation or plan change removes
How subscriptions grant credits Monthly vs annual — an annual plan is delivered as twelve monthly instalments, not up front
Dividing credits between sub-organizations and groups Budgets that move credits vs budgets that only cap spend
Credit usage limits and alerts Which limits warn and which block, the daily cap, percentage semantics, recipients, email frequency
Reading the Credits screen What each card counts and over what window; Credits by Type; the usage chart
View credit transactions Expanded with columns, filters and the CSV export

One correction

The expiry FAQ said purchased credits "do not expire" and complimentary credits "get reset at the beginning of each month." Both are inaccurate — purchased packs are valid for one year, and complimentary grants do not reset on the first of the calendar month. The FAQ now points at the new expiry section.

Unchanged

All per-feature rate tables — SmartUI, AI Test Case Generator, Conversational Layer, Test Case Deduplication, KaneAI authoring and real-device categories — are untouched, as are the commercial claims in Who gets credits?.

Notes

  • Content was verified against the credit service implementation rather than written from product description.
  • static/docs/credits-management.md regenerated with scripts/generate-static-md.js; no other generated file is included in this PR.

rahulgupta-02 and others added 8 commits August 26, 2026 17:48
…e Credits screen

The page covered per-feature credit rates but not how the credit system
itself behaves, which is where most support questions land. Adds:

- How credits are charged: metering, the hold-then-settle lifecycle, and
  why a run is refused before it starts
- Ways to get credits: dated batches, top-ups, requesting credits
- When credits expire: per credit type, burn order (soonest-expiring
  first), and what a cancellation or plan change removes
- How subscriptions grant credits: monthly vs annual (annual is delivered
  as twelve monthly instalments, not up front)
- Dividing credits between sub-organizations and groups: budgets that
  move credits vs budgets that only cap spend
- Credit usage limits and alerts: which limits warn and which block, the
  daily cap, percentage semantics, recipients and email frequency
- Reading the Credits screen: what each card counts and over what window
- Transactions: columns, filters and the CSV export

Corrects the expiry FAQ: purchased credit packs are valid for one year,
not indefinitely, and complimentary grants do not reset on the first of
the calendar month. Per-feature rate tables are unchanged.

static/docs copy regenerated via scripts/generate-static-md.js.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Both purchase links went to /billing/subscriptions?addCredits=true. Credits
now have their own screen, so send people straight there:
https://billing.lambdatest.com/billing/credits

Covers the "Upgrade / Buy Credits" link and the matching FAQ link, which
pointed at the same URL.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Adds five product screenshots alongside the sections that describe them:
the Credits overview, the Budgets list, the sub-organization and group
budget panels, and the Alerts screen. The two budget panels sit together
so their wording — "reserves credits from the root balance" vs "credits
stay in your org balance" — can be compared side by side.

Names and email addresses in the Top 10 Credit Users and Manage
Recipients tables were replaced with example.com sample data before
committing; no real account details are included.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The budget screenshots showed real sub-organization names, the group
name, and the selected values in the Sub-Organization and Group
dropdowns. Replaced with neutral sample data (Acme Retail, Acme
Payments, Acme Logistics, QA, qa_dev) drawn in the original font and
colours so the screens still read as genuine product UI.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
- Annual plan row now reads "11 further monthly instalments"
- Removes the tip stating that the lowest limit applies when budgets
  overlap

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The three remaining columns carry the decision the reader needs — whether
each alert emails and whether it stops usage. What the threshold is
measured against is already covered in the percentages section below.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The Alerts screen exposes only the warn threshold, the block threshold
and expiry alerts — there is no daily cap for an admin to configure, so
documenting one described a control that does not exist in the product.

Removes all seven references: the table row, the run-refused list, the
blocks-vs-warns bullet, the resume line, the 00:00 UTC note, the
percentage rule and the email-frequency row. The percentages section is
now prose, since only balance thresholds remain.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The heading described the layout rather than the content, which also made
it brittle if the card count ever changes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant