Give each client a proxy sub-user and traffic limit
A sub-user separates one client's credentials and usage from the main gateway account. It is useful when several tools or teams share a purchased traffic balance.
Create one identity per workload
Submit a sub-user request in Access with a distinct label, network and intended GB limit. The administrator assigns credentials and confirms activation and any gateway-enforced limit. A pending request is not an active account. Keep an application-side usage budget as well, and ask support to revoke or replace active credentials if they are exposed.
Set a realistic limit
Use the expected GB consumption plus a small margin. A limit that is too low stops valid work; an unlimited sub-user may spend the shared balance unexpectedly.
Review and revoke
Review the assigned credentials and actual usage after activation. Cancel a pending request if it is no longer needed. For active access, ask support to change the limit or revoke credentials and wait for confirmation before assuming access has stopped.
Worked example
Submit a sub-user request in Access with a distinct label, network and intended GB limit. The administrator assigns credentials and confirms activation and any gateway-enforced limit. A pending request is not an active account. Keep an application-side usage budget as well, and ask support to revoke or replace active credentials if they are exposed.
Common questions
Does a sub-user get a separate paid balance?
No. The limit controls consumption from the account's shared traffic. The account owner buys any additional traffic.
What if one client's credentials leak?
Submit a sub-user request in Access with a distinct label, network and intended GB limit. The administrator assigns credentials and confirms activation and any gateway-enforced limit. A pending request is not an active account. Keep an application-side usage budget as well, and ask support to revoke or replace active credentials if they are exposed.