Many LinkedIn accounts, one environment per rep, prospecting region by region
Several reps take turns signing into LinkedIn on one machine, sharing a fingerprint, a cookie jar and an exit IP. One account sends invitations a little too fast, gets restricted, and the others are asked to verify their identity - months of connections become unusable overnight. NexBrowser gives every rep and every target region its own environment and in-market IP, hands outreach to RPA, and leaves people to work the replies.
Free tier: 1 member and 10 windows, no expiry.
North America · Alex
203.0.113.24 · America/Chicago
SalesWestern Europe · Mia
198.51.100.77 · Europe/Berlin
SalesUnited Kingdom · Ray
203.0.113.91 · Europe/London
SalesSoutheast Asia · Lin
192.0.2.130 · Asia/Singapore
Sales4 regions · 12 rep environments · access managed centrally
Four places LinkedIn prospecting goes wrong
The accounts are fine. The trouble is that several people share one device, one connection and one pile of passwords.
Several reps, one machine
Reps take turns signing into their own LinkedIn in the same Chrome, leaving cookies and local storage behind and presenting an identical device fingerprint. When one account has a problem, the others on that machine are easy to associate with it.
The account gets restricted
Invite a little too quickly, or message strangers back to back, and LinkedIn asks for ID or drops the account into limited functionality. Connections stay, but search, invitations and messaging stop, and every follow-up sequence breaks with them.
The IP and language never match the market
Working North American buyers from an Asian exit with a Chinese interface means suggested contacts and job data do not reflect the market, and the opener you send reads as coming from nowhere in particular.
A rep leaves and the handover breaks the login
Handovers happen by passing credentials, so the next sign-in triggers new-device verification and kills the session. Revoking access after someone leaves means rotating the password and notifying everyone still using it.
The environment signals LinkedIn can actually read
LinkedIn stacks signals the same way. Separating environment from behaviour and identity tells you exactly where a tool stops helping.
- 01
Login IP and exit ownership
Several rep accounts signing in from one public exit in a short window is the most direct clue. Whether the IP is residential or datacenter, and whether its location matches the city on the profile, changes how often verification appears.
- 02
Browser and device fingerprint
Canvas, WebGL, audio, font list, resolution, timezone and language describe one device. Several reps sharing a byte-identical fingerprint tells the platform those accounts come off the same machine.
- 03
Cookies and leftover sessions
LinkedIn writes long-lived identifiers and device memories into cookies, localStorage and cache. Switching accounts inside one browser profile leaves the previous person’s identifiers on disk, and a handover in that profile trips new-device checks.
- 04
Outreach speed and rhythm
How many invitations you send a day, whether the openers are identical, how fast you page through search and whether you visit hundreds of profiles in a row matter more than device traits. A high share of ignored or "I don’t know this person" invitations is its own strong signal.
- 05
Verified identity and phone numbers
Out of a browser’s reach: accounts registered on one phone number, one ID document or in a batch under one company page are direct identity-layer evidence. Profiles have to be genuinely real and separate; a tool only owns the environment.
The conclusion is blunt: the first three layers are environment and separate cleanly with one fingerprint, one IP and one storage jar per rep; the fourth is rhythm, controlled by batching and scheduling; the fifth is identity and only separates if the profiles genuinely do. For how the isolation works, see multi-account isolation. For choosing exits by region, see residential IP and proxy setup.
Four capabilities behind LinkedIn prospecting at scale
Isolation, localisation, batched outreach and durable records - the whole pipeline in one workspace.
One rep, one account, one environment
A real Chromium core with 20+ fingerprint parameters per account, plus per-account cookie, cache and local storage jars, so reps never share browser traits and a handover does not break the session.
Local IPs for the market you sell into
Work North American buyers on a North American residential IP and European buyers on a European one, with timezone and language to match, so search results, suggested contacts and job data reflect the real market.
Outreach in controlled batches
No-code RPA turns connection requests, openers and follow-ups into scheduled runs that work a list in batches, record the outcome and retry failures, while window sync repeats one action across several accounts.
Keep the prospect data yourself
The free Local API, with no call limit, connects Selenium, Puppeteer or Playwright to turn public company and role data into structured tables you export straight into your existing CRM follow-up.
Four steps to move team accounts into separate environments
Accounts already prospecting can migrate smoothly. Start with the two or three regions that close the most.
- 1
Create environments
Add one environment per rep or target region with a fingerprint template consistent with a real device. Name them "region + rep" and group them by team so growth does not turn the list into a mess.
- 2
Bind proxies
Pick a residential IP in the region your buyers sit in, bind it to the environment and match timezone and language to it. Run the availability check to confirm the exit country before opening LinkedIn.
- 3
Import accounts, assign people
Import existing cookies or sign in once inside the new environment; the session persists. Assign accounts by role to the right reps and managers, who open them already signed in and never see a password.
- 4
Reach out in batches
Hand invitations, openers and second follow-ups to RPA, schedule them on the buyer’s local time with a daily cap, and keep people for the replies and the conversations that need a human.
Migrate one account at a time and work normally in the new environment for a few days before moving the next. For driving several accounts at once see window sync, and for turning outreach into scheduled jobs see no-code RPA.
Three reasons export teams pick it
Separate environments, faster outreach, data you keep.
Environments that are real and reproducible
A real Chromium core plus 20+ internally consistent fingerprint parameters, so LinkedIn, Sales Navigator and the extensions your team uses all load normally - and the same environment presents the same device every time.
Role-based access, no shared passwords
Assign accounts to reps and managers by role, sync encrypted configuration to the cloud, and let people work inside an already-signed-in environment. Access is revocable instantly and every session leaves a trail, so staff changes stop being account risk.
A free tier you can actually work in
1 member and 10 windows free forever with no feature gating - enough to isolate the accounts in your main regions and see the result. Add windows and seats as you grow; the local API is free with no call limit.
Give your two strongest regions an environment each
Download the Windows client, isolate your core rep accounts in the 10 free windows, then decide whether to scale.
LinkedIn multi-account questions, answered
My LinkedIn account is restricted - what should I do?
Stop every bulk action, complete the identity check LinkedIn asks for, and do not change device or exit IP during the review, because a drifting environment lengthens it. When access returns, cut the daily invitation volume to a third, rewrite openers so they reference the specific company and role, and spend two weeks mostly browsing and engaging. Most restrictions come from outreach speed and ignored invitations, not from what you wrote.
How many LinkedIn accounts can one computer sign into?
At the device layer there is no hard limit: each account runs in its own environment, and 8GB of RAM handles a dozen windows comfortably. LinkedIn’s user agreement, however, expects one real person per account. The correct team pattern is one genuine account per rep, with the company managing environments and access centrally - not one person driving a set of invented identities.
Can several LinkedIn accounts get linked to each other?
Yes, when they share a device, an exit IP and a batch of registration numbers. LinkedIn combines device fingerprint, login IP, cookie identifiers and action rhythm to judge how accounts relate. Giving each rep a separate environment and a local IP removes the device and network layer from that picture; whether the profiles themselves are genuinely independent is on the company.
How do I hand over an account without losing the session?
The account already lives in a team environment, so the handover is a permission change: move access from the departing colleague to whoever takes over. The environment, fingerprint and proxy binding are untouched, the session persists, no password changes hands and no new-device verification fires. Access for the person leaving stops immediately, and the record shows who used which environment and when.
Which IP should I use for buyers in different countries?
Pick a residential IP in the region your buyers are in, keep one account on one relatively stable exit long term, and set timezone and language to match. North American prospecting runs on a North American line, German buyers on a German one, and search results and suggestions follow. Avoid hopping between countries in a single day - that triggers verification faster than staying put.
Is it safe to send connection requests with RPA?
The risk is not the tool, it is speed and relevance. Keep the daily invitation volume inside what the account’s age supports, put the specific company or role into the opener, send in batches on the buyer’s local time, and clear out ignored requests regularly. RPA earns its place by fixing that rhythm and recording what ran, not by making the actions faster.
Have other questions? We're here to help anytimeContact Support →
Related reading
- Social media matrixOne workspace for multi-platform account matrices
- Twitter/X multi-accountAccount matrix and synchronised publishing
- Multi-account isolationHow 20+ fingerprint parameters and separate storage work
- Residential IP and proxiesBind an in-market exit and check it before login
- No-code RPAInvitations, openers and follow-ups as scheduled jobs
- Local APIDrive Selenium or Playwright and export structured data
Ready to manage every account profile in one place?
Install in 3 minutes. 10 free windows on sign-up, no credit card.
Free Download for WindowsAlready have an account? Sign in to the client to sync all profiles.