Customer administration

Hosted customers, invitations and roles.

Hosted customers, invitations and roles.

This screen belongs to the Secure deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.

Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.

Step-by-step actions

  1. Open Customers administration → + Add customer.
  2. Enter name, email, unique ID, monthly cap, RPS and Burst.
  3. Choose access and notification settings; Create and invite saves the record and sends an invitation.
  4. Open an existing row, edit limits/access and Save settings.
  5. Send invitation and Notify about saved settings are separate email actions; check saved settings first.

Every control and its meaning

Control / parameterValues, units and effect
Компания / имя, Email, ID клиентаName up to 200 and email up to 254 characters. ID uses 1–63 lowercase letters/digits with internal hyphens. Existing email/ID are not editable.
Запросов в месяц (UTC)Integer ≥ 0; 0 means unlimited, for example 10000. This is a monthly request cap, not a token cap.
Запросов / секунду, BurstRPS 0–100000; Burst integer 1–1000000. Example: 10 RPS and burst 20. These ranges differ from the dynamic quota form.
Доступ разрешён / Access enabledDisable to deny this customer access; save the setting. This does not disable protection for other customers.
Уведомления, Внутренняя заметкаNotifications permit email delivery; internal notes are up to 4000 characters. Enabling the flag does not send an email on its own.

Verify the result

Refresh and reread the record; verify invitation status and customer access to their own tenant. Disabled customers should be denied; test limits using their key.

Errors, disabling and reverting changes

A failed email may leave a saved customer record: refresh the list, repair delivery and resend separately. Restore prior limits/flags and save to revert.

Customer: saved limits 90 / 8 RPS / burst 16
Customer: saved limits 90 / 8 RPS / burst 16
2026-10-15 · Working staging, synthetic customer only. Values were saved in the form, read after a full reload and shown to the customer. Sign-in suspension and restoration were checked separately; final values were restored to 100 / 10 / 20 with access enabled. No emails were sent.
  1. Monthly requests
  2. Requests per second
  3. Burst
  4. Access enabled
  5. Save settings
Customer: saved limits 90 / 8 RPS / burst 16
Customer: saved limits 90 / 8 RPS / burst 16
2026-10-15 · Working staging, synthetic customer only. Values were saved in the form, read after a full reload and shown to the customer. Sign-in suspension and restoration were checked separately; final values were restored to 100 / 10 / 20 with access enabled. No emails were sent.
  1. Monthly requests
  2. Requests per second
  3. Burst
  4. Access enabled
  5. Save settings

Detailed security settings · Traffic analysis · FAQ · All application sections