👥 Sub-Accounts

Sub-accounts allow you to divide your proxy access across multiple users, projects, or clients — each with isolated credentials, pool assignments, and traffic quotas.

What Are Sub-Accounts?

A sub-account is a child account under your main account. Each sub-account has:

• Its own username and password
• Assigned proxy pools from your account's available pools
• A traffic cap per pool — a ceiling on how much of your shared main balance that sub-account can draw, not a separate reserved allocation. A cap of 0 means unlimited traffic for that pool (limited only by your main balance).
• Independent usage statistics, viewable within each pool's Statistics section
• No visibility into other sub-accounts or the main account

Sub-Account Limit

By default, you can create up to 5 sub-accounts per main account. If you need more, contact support — the limit can be increased upon request.

Creating a Sub-Account

1. Go to Dashboard → Sub-Accounts.
2. Click Create Sub-Account.
3. Set:
   • Login — username for the sub-account
   • Password — password for the sub-account
   • Pools — select which pools this sub-account has access to (you can assign multiple pools)
   • Traffic cap — a per-pool ceiling on usage drawn from your main balance (0 = unlimited for that pool)
4. Click Create.

The sub-account can now use X2Proxy with its own credentials. The proxy format follows the same structure as the main account:

http://pool_category;SUB_LOGIN:SUB_PASSWORD@pr.x2proxy.com:2222

All of the above — creating sub-accounts, editing pool caps, enabling/disabling — is also available through the API.

Pool Assignment

When creating or editing a sub-account, you can assign access to any combination of pools available on your account — for example, the Stable residential pool, the Dynamic residential pool, or future pool types as they become available. Each assigned pool can have its own traffic limit.

This makes it easy to allocate specific pool types to specific projects or clients — for instance, giving a client that needs sticky sessions access only to the Stable Pool, while a scraping team gets access to the Dynamic Pool.

Use Cases for Sub-Accounts

Scenario	How to Use
Agency / reseller	Create one sub-account per client; assign pools and traffic per contract
Team access	Give each team member their own credentials and pool access
Project isolation	Separate traffic per project to track usage and costs accurately
Pool segmentation	Restrict sub-accounts to specific pools relevant to their workload

Managing Traffic Caps

• Traffic is deducted from the main account balance when a sub-account uses it — the cap is a ceiling on that shared balance, not a separate pool of traffic.
• You can adjust caps at any time from the dashboard or via the API.
• Sub-accounts cannot transfer traffic to other sub-accounts.
• If a sub-account reaches its cap, it stops working for that pool until you raise the cap.

Monitoring Sub-Account Usage

Sub-account statistics are available in two places:

• Dashboard → Sub-Accounts — overview of all sub-accounts, traffic used/remaining per account, last activity
• Dashboard → Statistics (inside each pool) — detailed usage data filtered by sub-account, including request volume and geographic distribution

Changing Credentials

You can reset the password or update pool assignments for any sub-account from the dashboard at any time. Changes take effect immediately.

Disabling a Sub-Account

To temporarily suspend access without deleting the sub-account, use the Status toggle (Enabled / Disabled). Re-enable it at any time.

Note that setting a pool's traffic cap to 0 does not disable the sub-account — a cap of 0 means unlimited traffic for that pool. Use the Status toggle to actually disable access.

---

Next: Traffic & Usage