Sharing Proxies With a Team: Assign, Manage and Revoke
Updated:
The safe way to share proxies with a team is to tie each proxy to a specific account rather than a person, hand out work through antidetect browser profiles instead of sending raw ip:port:user:pass strings, record every assignment in one register, and follow a clear revocation routine when someone leaves or changes role. That way staff can do their jobs without holding proxy credentials, and when someone leaves you do not have to guess who is using which IP. This guide covers the process step by step, a register template and an offboarding checklist.
What goes wrong with ad hoc sharing
Many teams start by pasting a proxy list into a group chat and letting everyone help themselves. A few months later the results are predictable: two people accidentally use the same IP for two accounts on the same platform, nobody remembers which IP belongs to which account, proxies expire because no one renewed them, and former staff still have the list on their laptops.
Each problem is small, but together they break the most basic rule of multi-account work: one dedicated, static IP per account. Our multi-account setup checklist explains why that rule matters.
Assignment principles
- Proxies belong to accounts, not people. When the person in charge changes, the account keeps its IP and the new owner inherits both.
- One person buys and manages: only the team lead or operations owner logs into the provider dashboard, tops up, orders and renews. Staff do not need dashboard access.
- Staff see only what they need: give them antidetect profiles with the proxy already attached, never proxy strings in chat.
- Group by task and country: for example one batch of Vietnam IPs for the domestic shop team and one batch of US IPs for the US market team. Easy to count and renew.
- Keep a few spare IPs so you can replace a failing proxy quickly instead of borrowing one that already serves another account.
Hand out proxies through antidetect profiles
Most antidetect browsers have team features: the lead creates a profile, attaches a proxy and shares the profile with a member. The member opens it and works but never needs to know the proxy details. When the profile is revoked, access ends immediately.
This solves two problems at once: staff cannot take the proxy elsewhere, and they cannot accidentally attach one proxy to two profiles. If you have not picked a browser yet, see how to choose an antidetect browser; proxy setup guides exist for GenLogin, AdsPower, Hidemyacc and many more in our setup section.
If you must give someone the proxy details, for example to configure a phone or a separate tool, share them through a team password manager with permissions, not through chat or email.
A proxy register template
A shared spreadsheet is enough for most small teams. The key is that only one or two people can edit the IP column.
| Column | Example | Purpose |
|---|---|---|
| Proxy IP | IP only, never the password | Quick lookup, prevents duplicates |
| Type and country | Dedicated IPv4 VN, ISP US | Know which type serves which task |
| Assigned account | Shop A on marketplace X | Ensures one IP per account |
| Antidetect profile | Profile name or ID | Find the right profile fast |
| Owner | Staff member | Know what to revoke when people change |
| Expiry date | From the dashboard | Renew early to keep the IP |
| Notes | Incidents, IP changes, reasons | Spot patterns when problems appear |
Renewals and routine checks
- Renew on the dashboard before the expiry date to keep each account's IP. A lapsed proxy may not keep its old IP.
- Run the whole list through the proxy checker weekly to catch failing IPs early. Checking whether a proxy is alive has the details.
- Compare the register with the dashboard: any IP you pay for that is not assigned to an account should be reviewed before renewal.
- When something breaks, staff raise an internal ticket to the manager rather than swapping proxies themselves. The manager contacts the provider's support by ticket if needed.
Offboarding checklist
- Revoke every antidetect profile shared with the person and remove them from the browser's team workspace.
- Remove their access to the password manager and the register.
- Change passwords on platform accounts they knew, and recheck recovery email and phone settings.
- If they ever held proxy credentials in plain text, treat those credentials as exposed and contact the provider's support by ticket to ask how best to handle it.
- Update the owner column and hand the accounts and proxies to the new person.
- Log the revocation date so you can cross-check any odd activity later.
Frequently asked questions
Should every employee have their own proxy purchasing account?
Usually not. Central purchasing and management make cost control, renewals and revocation much easier. Staff only need profiles with proxies attached.
Can two employees share one proxy?
Yes, if they both work on the same account. Do not put two accounts on the same platform onto one IP just because two different people run them.
Does it matter if staff work from home or elsewhere?
If they work through an antidetect profile with a fixed proxy, the platform still sees the proxy IP. Run a WebRTC leak test on any new machine to make sure the real IP is not exposed.
Do VinaProxy proxies limit how many devices use one IP?
Proxies authenticate by username and password, each IP is assigned to one customer and bandwidth is unlimited. How many people use it is something you manage internally.
How do I know staff are not using proxies for other things?
The surest way is not to give them the proxy details at all and share only antidetect profiles. Without the proxy string they cannot use it elsewhere.
Buy proxies centrally for your whole team
Pay in VND from your balance, automatic activation, renew to keep the same IPs. Dedicated IPv4 in 7 countries and static ISP in Vietnam and the US.
See pricing