As soon as the team has more than two or three people working with Facebook Ads, TikTok Ads, or marketplace accounts, the question of "who gets which proxy" stops being trivial. An incorrect scheme can lead to a chain of bans across the team, wasting the advertising budget, and disputes over "who is responsible for the block." We will analyze when it is more beneficial to have a personal proxy for each employee and when a shared pool can suffice, and how to account for all this without chaos in spreadsheets.
Why the issue of proxy accounting is critical for the team
While there is one person in the team, a proxy is simply a technical setting in an anti-detect browser. But when there are 5, 10, or 50 employees simultaneously managing Facebook Ads accounts, Instagram client accounts, or scraping prices on Wildberries, the proxy management scheme becomes part of the operational security of the business.
Imagine a situation: the agency has a shared pool of 20 proxies, which are distributed to employees "as needed" without tracking who is using which IP. One employee gets their account banned for suspicious activity — and the platform's security system marks that IP as risky. A day later, the same address is accidentally assigned to another employee, and their account gets banned "by association." A week later, three teams are panicking, and figuring out where the chain started is impossible — no one kept track.
This is a classic problem of multi-accounting at the team level. It is not solved by purchasing more expensive proxies, but by properly organizing the process: who, which IP, for which account, and how much traffic is being used. We will further analyze both models — shared pool and personal proxies — and show where each is appropriate.
Shared proxy pool: when it works
A shared pool is a set of proxies available to all employees through a single panel or proxy manager, from which each takes an IP as needed. This scheme works well for tasks where long-term binding of an account to a specific address is not required: one-time scraping of competitor prices on Ozon, checking Yandex.Direct results from different regions, mass verification of ads on Avito.
For such tasks, data center proxies are often sufficient — they are fast, inexpensive per IP, and are great for short sessions without binding to a specific account. If the task is to collect a price snapshot once a day from 500 product cards, it doesn't matter who from the employees did it and from which IP: an account is not needed, and the risk of blocking is minimal.
However, a shared pool is dangerous where personalized accounts are involved: Facebook Ads accounts, Instagram profiles, personal seller accounts on Wildberries. Platforms analyze the combination of "account + IP + device (fingerprint)" and remember this pair. If today Ivan accessed a client's account from IP 1, and tomorrow Maria accessed the same account from IP 2 — this looks like suspicious activity because not only the address changes, but the entire digital environment of the session does as well.
Conclusion: a shared pool is suitable for operations without permanent accounts. For managing advertising accounts and social media profiles, it creates more risks than it saves money.
Personal proxy for each employee
The personal model assigns each employee (or rather — each account or profile in the anti-detect browser) their own static IP that does not overlap with others. This is the standard for agencies that manage clients' accounts in Facebook Ads, TikTok Ads, Instagram, or handle personal accounts on marketplaces.
The logic is simple: if the IP is always the same for a specific account, the platform sees a stable, "home" picture of access — the same region, the same provider, the same session. Anti-fraud algorithms react specifically to anomalies: a sudden change in geolocation, a data center IP instead of a regular home address, simultaneous logins from different parts of the world. A personal proxy eliminates these anomalies at the root.
For this scheme, residential proxies are most often used — they provide real IP addresses from home providers that are indistinguishable from regular internet users. For tasks where the mobile signature of the network is critical (for example, farming TikTok or Instagram accounts, where the platform checks the type of connection), mobile proxies are used — their IP belongs to a mobile operator, and rotation occurs naturally, just like on a real smartphone.
The downside of the personal model is the cost. More IPs mean higher infrastructure costs. But for an agency that is responsible to the client for the safety of the advertising account, this is a justified expense: one banned account with a budget of 500,000 ₽ on advertising costs more than a year of personal proxies for the entire team.
Comparison table: pool vs personal proxy
Let's summarize both models in a table to make it easier to make a decision for a specific department or task.
| Criterion | Shared Pool | Personal Proxy |
|---|---|---|
| Cost for the team | Lower, IPs are shared | Higher, 1 IP per account/employee |
| Risk of chain ban | High | Minimal |
| Suitable for advertising accounts | No | Yes |
| Suitable for scraping without accounts | Yes | Excessive |
| Ease of traffic accounting | More complicated — requires a logging system | Easier — traffic is tied to IP |
| Recommended type of proxy | Data Center | Residential / Mobile |
Chain bans and security risks when sharing
A chain ban is a series of blocks when the platform links several accounts through common characteristics: one IP, one device fingerprint, one payment card, one cookie file. If the team shares proxies without accounting, the risk of triggering such a chain grows proportionally with the number of employees.
A common scenario in SMM agencies: Manager A manages 10 client Instagram accounts through one IP from the pool. One of the accounts receives a complaint and gets blocked for suspicious activity. Instagram checks the IP and finds 9 other accounts that accessed from the same address over the past weeks — and bans the entire chain, including accounts managed by Manager B, who was not involved in the incident at all.
The second risk is access leakage. When proxies are shared and connection data is stored in one Excel file with the password "1234," when an employee is fired or a contractor is changed, the entire pool must be changed, not just one address. This slows down work and creates a window of vulnerability.
The third risk is session conflicts. If two employees accidentally use the same IP simultaneously for different accounts on the same platform, the security systems of Facebook or TikTok detect parallel sessions from one address and may block both accounts "just in case," even if nothing illegal was happening.
These risks can only be reduced by firmly binding the "account — IP — profile in the anti-detect browser" and not changing it unnecessarily. That is why for accounts with advertising budgets, the personal model almost always wins over the shared pool.
How to organize traffic accounting by employees
Traffic accounting solves two tasks: budget control (who spent how many gigabytes or hours on proxies) and security auditing (who accessed from which IP and when). Here is a working scheme for a team of 5 or more people.
Step 1. Assignment table. Maintain a single registry: employee → account/client → proxy IP → date issued → type of proxy (residential/mobile/data center). Google Sheets with limited editing access will work — only the team lead or department head can change records.
Step 2. Provider's personal account. Most proxy services provide a personal account with statistics on traffic consumption for each individual IP or port. Check the consumption weekly — a sharp spike in usage by one employee may indicate excessive automation, access leakage, or a simple configuration error.
Step 3. Logging in the anti-detect browser. Dolphin Anty, AdsPower, and Multilogin store the history of which profile logged in and when, through which proxy. Regularly compare these logs with the assignment table — discrepancies signal a violation of regulations.
Step 4. Limits per employee. If the provider supports traffic-based billing, set a conditional limit per person or department (for example, 50 GB per month for an SMM specialist managing 20 accounts). This disciplines the team and simplifies budget forecasting for infrastructure.
Step 5. Regular rotation of responsibilities. If an employee leaves or moves to another project, immediately reassign the IP to the new responsible person and record it in the registry — do not leave "orphaned" proxies hanging without binding.
Setting up roles in Dolphin Anty and AdsPower
Anti-detect browsers were originally designed for teamwork, so they have built-in access distribution tools. In Dolphin Anty, there are team spaces: you create a workspace for the agency, add employees by email, and assign each access only to specific browser profiles. Proxies are not tied directly to the employee but to a specific profile — so even if access to the profile is transferred to another person, the "account + IP" combination does not change.
In AdsPower, a similar logic applies: there is a group management function where you create profile groups by clients or directions and grant rights to individual team members — some can only view, some can edit, and some can launch. The proxy is specified at the profile level in the connection settings section, and when exporting reports, it is clear which IP was used in each session.
Practical recommendation: create one anti-detect browser profile for one client account, not for one employee. If an employee goes on vacation or leaves, you simply transfer access to the profile (with all cookie history, fingerprint, and attached proxy) to the next person — the client account does not see any difference because the digital fingerprint of the session does not change.
This approach resolves the main conflict between "shared" and "personal" proxies: the proxy is personal not for the person, but for the account/profile, and people can swap places without risk to the client's business.
What type of proxy to choose for the team
The choice depends on the task of a specific department within the team, not on a general rule of "the same for everyone." Here is a practical distribution by agency or arbitration team work directions.
For the department managing clients' Facebook Ads and Google Ads accounts, residential proxies tied to the client's region are suitable — they appear most natural to the anti-fraud systems of advertising platforms and allow maintaining a stable geolocation for the account for months.
For the SMM department, which farms and manages Instagram and TikTok accounts, it is wiser to use mobile proxies — social networks are more likely to trust traffic from mobile operators, especially when logging in from a phone or emulating a mobile device in an anti-detect browser.
For the analytics department, which monitors competitor prices on Wildberries, Ozon, or collects data from Avito without tying to personal accounts, data center proxies are sufficient — they handle large requests faster and are cheaper per number of IPs.
Such segmentation by departments, rather than by individuals, immediately resolves half of the questions about "shared or personal proxy" — because the answer depends on the task, not on the staffing schedule.
Implementation checklist for the proxy accounting scheme
Before changing the current scheme in the team, go through this list:
- Are departments with accounts (advertising, SMM) separated from departments without accounts (scraping, analytics)?
- Is a personal proxy assigned to each advertising and social media account?
- Is there a unified registry "account — IP — browser profile — responsible" maintained?
- Are access roles set up in Dolphin Anty / AdsPower at the profile level, rather than using shared passwords?
- Is there regular reconciliation of traffic statistics with the provider's personal account?
- Is there a procedure for transferring access upon employee termination or transfer?
- Is data center proxy used only where there are no personalized accounts?
If the answer to most of the items is "yes" — the risk of mass bans and traffic confusion for the team is minimal.
Conclusion
A shared pool and personal proxy are not mutually exclusive options, but tools for different tasks within one team. A shared pool saves budget where there are no permanent accounts — for scraping and one-time checks. A personal proxy is essential where there are advertising accounts, client profiles, and account reputation, which can easily be lost with one unsuccessful IP change.
The key idea is to tie proxies not to the employee, but to the account or profile in the anti-detect browser, and to maintain a unified accounting registry. Then, the rotation of people in the team does not create risks for client projects. If you are just building such a system, start with distributing tasks by types of proxies: residential proxies for advertising accounts, mobile proxies for social media, and data center proxies for analytics and monitoring — this will cover most team work scenarios without unnecessary costs and without the risk of chain bans.