Set up proxy routing

A proxy pool groups network endpoints. An account assignment chooses the pool an account should use. Importing a pool, assigning it and establishing a working account connection are distinct steps.

Members need Proxies access to manage pools and assignments. Assigning from the Steam account directory also needs Steam access. Ask an owner to review workspace permissions if a control is unavailable.

Connect a proxy provider

Use Connect provider in Proxies to connect a supported provider account you already use. This is separate from importing an endpoint list.

1. Choose Webshare Residential, Webshare Static or Proxyline to match your provider service.
2. Prepare that provider account's API credential:
   • For Webshare, use an API key from your Webshare dashboard's API Keys page. See Webshare's API authentication guidance.
   • For Proxyline, use the API key from your Proxyline account. See Proxyline's API guidance.
3. Paste the credential itself into API token. This is not a proxy endpoint's username or password, a full proxy URL, or a Goldmine API key.
4. Submit the connection once and review the reported result. A confirmed provider connection has its own routing pool; provider state and endpoints may still be updating. Check the pool and available capacity before assigning it to Steam accounts.

Keep provider API credentials private. A saved provider connection does not prove an endpoint is reachable or that a Steam account is connected.

Import an existing proxy list

Open the proxy list import in workspace setup or the proxy area. This imports endpoints you already have; it does not buy proxies or expand a provider plan.

1. Enter a recognisable name for the new pool.
2. Choose your proxy file. The import accepts CSV, TSV, JSON or TXT files up to 8 MiB.
3. For a table file, check the column mapping for Host / IP, Port, Username, Password and Scheme. For TXT, each row must be a supported proxy URI.
4. Review the valid and skipped row counts. Correct invalid endpoints before relying on the pool.
5. Submit the import and inspect the outcome. Each file creates a new imported pool; successful rows are not automatically resubmitted.

Keep provider credentials and authenticated proxy URLs private. If an import is interrupted or its result is unclear, inspect the pool before submitting the same file again.

Assign a pool to Steam accounts

From the Steam account directory, select the intended accounts and choose Assign proxy pool. You can also assign a pool from an individual account's connection view. Check the pool name and captured account selection before confirming.

The result reports an acknowledged count, not a success or failure for each named account. Accounts pinned to another pool keep their assignment; bindings that changed during the request can also be excluded. Use Review current assignments to inspect the saved result. If assignment was acknowledged but the displayed data could not be updated, recover that read instead of repeating the assignment.

Changing a pool changes the account's configured routing. It does not prove an existing Steam connection has switched to that route. Check the account's connection state separately.

Change one saved assignment

In Assignments, find the exact account and inspect its saved pool and endpoint. Edit changes the endpoint or pin setting; Rebind asks the pool to choose a binding and is unavailable for a pinned assignment. A rebind may keep the existing endpoint. Delete removes the saved assignment and may release its dedicated residential endpoint; shared endpoints are kept. Read the confirmation before proceeding.

After a change, Review change shows the captured account and outcome when you close the dialog or leave and return in the same signed-in workspace:

• Awaiting acknowledgement: wait for the response. Navigation cannot undo a request already sent.
• Request acknowledged: the service acknowledged the change. If displayed data still needs updating, use Read current assignment data instead of repeating the command.
• Change outcome unconfirmed: inspect current assignment data, but keep the earlier outcome separate. A matching record does not prove what that command did.

When offered, Start new decision only lets you choose a current assignment and confirm a separate change. It sends nothing by itself and does not confirm or cancel the earlier uncertain request. A pending request cannot be unlocked this way. For a rejected edit, Edit rejected change returns to the submitted changes so you can correct them.

Assign during workspace setup

The setup assignment step uses the pool imported in that setup run and the workspace accounts shown in its roster. It is not the selected-account action from the account directory.

1. Import the intended pool, then open Confirm account assignment.
2. Wait for the full account roster to load and resolve any roster error. If it exceeds the supported assignment size, use smaller selections outside setup.
3. Check the pool and affected accounts, then choose Assign accounts to pool.
4. Read the acknowledged count against the accounts submitted. The final review distinguishes Assignment response pending, Assignment outcome unknown and recorded assignments whose coverage has not been checked.

If no pool was imported in this run, setup leaves existing assignments unchanged. Use Review account assignments to inspect or manage them.

If the assignment outcome is unknown

Changing setup steps does not make an uncertain assignment safe to repeat. Setup retains the attempted pool and account list and prevents another assignment or replacement pool import from that attempt.

In Check a saved binding, choose one Submitted account, then select Check saved assignment. The result can show the imported pool, another pool or no returned assignment, plus any recorded session. This checks that account's saved configuration; it does not confirm what the earlier command did, establish coverage for other accounts or test the Steam connection. The assignment outcome remains unknown after the check.

Use the current assignment records when deciding what needs attention. Do not restart setup or import the same pool merely to get past the unknown outcome.

Understand what is ready

A saved assignment alone does not prove an endpoint is reachable or a Steam account is connected. Review the account's connection state after assignment.

If no usable session is available, check the selected pool, endpoint details, authentication and capacity. A provider's account or inventory count is not a substitute for available routing capacity. Do not repeatedly import or reassign accounts to work around a provider limit.

If the connection message says the proxy rejected authentication, inspect the account's assigned endpoint in Proxies. This is separate from Steam rejecting account sign-in details; those are reviewed in the account's Credentials. Neither message proves that changing an assignment has repaired the current Steam connection.

Next, return to Steam accounts and check the connection.