How to use Quotas

Sets and shows tenant request, token and budget limits with current consumption.

What this section is for

Sets and shows tenant request, token and budget limits with current consumption.

Before you start

You need access to IAM.Router, the correct tenant/workspace and permission to change this configuration. Prepare a non-sensitive example value such as tenant-demo.

Buttons and forms

ControlWhat it does
Edit quotaPerforms the action named in the interface. Review the resulting state or message before continuing.
SaveValidates the visible form and persists the current values.
RefreshReloads data from the server and keeps the current page context.

Primary path in the interface

  1. Open the application link above and sign in with the least-privileged role required for this section.
  2. Select the intended tenant or workspace. Do not continue while the header shows a different tenant.
  3. In the navigation, click Quotas. The expected address is https://app.iamrouter.ru/quotas.
  4. Click Edit quota. Enter the documented safe values: tenant-demo. Do not paste a production secret into a free-text field.
  5. Review every field before the final Save, Run, Publish or Confirm action. If a preview or validation control exists, run it first.
  6. Review the validation message or changed row. The result must match this purpose: Sets and shows tenant request, token and budget limits with current consumption.
  7. Only then continue to the next dependent section. Copy the request/correlation ID when the interface shows one.
  1. Open the deep link https://app.iamrouter.ru/quotas instead of navigating through the sidebar.
  2. Confirm the tenant/workspace after the page loads; a deep link must not silently switch scope.
  3. Before automating the API path, run this product-specific read-only or validation command. It proves reachability but does not bypass application permissions:
export IAM_ROUTER_URL=https://api.iamrouter.ru
export IAM_ROUTER_TOKEN='<token>'
curl --fail --silent --show-error "$IAM_ROUTER_URL/healthz"

How to verify the result

The new quota is active, usage cannot exceed it without the expected 429 and the reset window is known.

If it did not work

SymptomWhat to do
401 / sign-in screenSign in again, then return to this page. Do not put a session token in a URL.
403Check the selected tenant and request the documented role; retrying with the same role will not help.
404Verify the exact path and whether the feature is enabled in this environment.
409Search for an object named tenant-demo; continue with it or choose a unique name.
422 / validation errorCorrect only the highlighted fields. Keep identifiers lowercase unless the form explicitly allows otherwise.
429Wait for the displayed retry interval or reduce the request scope; do not start parallel retries.
5xx / timeoutRefresh once after the server has recovered; do not repeat a destructive action while its result is unknown. Save the correlation ID and timestamp for support.