Multi-Account Browsers for Teams and Agencies FAQ: 16 Questions Answered for 2026

Profiles often get lost in agency teams for a simple reason: nobody documented which team member created them, and under which login.

That's not a technology problem. It's an operations problem that technology should have prevented — and honestly, in 2026, many multi-account browsers still handle team workflows awkwardly. The tools were built for solo operators running their own accounts, then had "team features" bolted on as an afterthought. You can tell.

This FAQ covers the questions that agencies and teams actually ask. Not the basic "what is browser fingerprinting" stuff you can find anywhere. The operational reality of running a multi-account browser across multiple people, multiple clients, and billing setups that make accountants cry.

1. How much does team access actually cost?

Let's do the math. JustBrowser is one plan — $9.99/mo, or $99.99/year — with unlimited profiles, and team seats on top of it are free and unlimited. A 5-person agency pays $9.99/mo.

Understand the shape of that before you plan around it, though. A free seat can only run profiles someone has shared with it. It can't create profiles of its own, can't cloud-sync them, can't use the REST API. So the question isn't headcount — it's how many people need to build profiles rather than work inside them. One operator building for four people to run: $9.99/mo. Five people who each build their own: five subscriptions, $49.95/mo.

Compare that to the tools that price per seat or per profile tier (see Multilogin, GoLogin and AdsPower's published pricing pages for current numbers).

The per-seat model trips up a lot of agencies because headcount fluctuates. You bring on two contractors for a campaign, you need two more seats. Campaign ends, you're still paying or dealing with the hassle of removing them. That specific mistake is the one free seats make impossible: an idle seat costs nothing, so forgetting about one costs nothing either. If you're weighing tools that do bill per seat, check whether they lock you into annual seat commitments before you sign.

2. What's the difference between seats and profiles?

This confuses everyone at first. Profiles are the browser instances — each one with its own fingerprint, cookies, and identity. Seats are user logins — how many humans can get into the dashboard.

On JustBrowser there's one plan, and it gives you unlimited profiles and unlimited free seats. You're not paying per-profile or per-person.

What a seat is not is a second subscription. A seat runs profiles that have been shared with it, and that's the whole entitlement — no creating its own, no cloud sync, no API tokens. Think of it as a key to someone else's profiles rather than a licence of its own.

The implication? 500 client profiles and ten people running them, on one $9.99/mo subscription, as long as one person is the one creating them. Agencies where account managers execute inside profiles but never build them fit that shape almost exactly.

3. Can team members see each other's profiles?

Depends entirely on how you set up permissions. Most tools offer:

• Shared folders visible to everyone
• Private folders visible only to the creator
• Role-based restrictions where admins see everything, operators see assigned clients only

On JustBrowser, sharing is the permission model. A seat doesn't browse a global pool — it sees the profiles that have been shared with it, and nothing else. Juniors get the client profiles they're actually working on, and nobody has to remember to lock down the rest.

The gotcha: some tools don't have granular permissions at all. Everyone sees everything, or you create separate sub-accounts and lose the benefits of shared infrastructure. Frustrating. If you're managing sensitive client accounts (especially anything with banking or payment info stored in profiles), permissions aren't optional — they're the whole point.

4. What happens when someone leaves the agency?

This is where most agencies get burned.

Profiles belong to the account, not to individual seats. When you remove a user, profiles they created stay behind. But here's the problem: if profiles were created in someone's personal folder and that person leaves on bad terms... you might have access, but you won't know which profiles exist or what state they're in.

What works: require all client work to happen in shared team folders from day one. Make it policy. No exceptions. Individual "testing" or "personal" folders are fine for experimentation, but nothing client-facing lives there. Ever.

On JustBrowser there's nothing to transfer, because a seat never owned anything: profiles live with the subscription that created them, and the seat only ever had permission to run them. Offboarding is removing a person, not untangling ownership. Worth checking how your own tool handles it — some make you export and re-import profiles by hand, which is annoying and error-prone.

5. How do agencies handle billing to clients?

Three common approaches:

Bundled into management fee. You're paying $9.99/mo for a team managing 50+ clients. That's about 20 cents a client. Nobody itemizes that. It's part of the cost of doing business.

Platform access line item. Some agencies add a flat monthly "platform access" fee per client. They're paying cents in actual cost and charging a flat fee. That's margin. (That's a business choice — clients who want itemized invoices can run their own tooling. Most don't want to.)

Pass-through at cost. Rare, but some agencies do this for enterprise clients who demand transparency. You show them the $9.99 line and split it pro-rata, which at this price is almost comedy. Transparent, though it leaves margin on the table.

Option 3 is for compliance-heavy clients who audit vendor costs.

6. How do we onboard new team members without compromising profiles?

Here's the SOP that works for a 10+ person team:

1. Invite them as a seat — free, and structurally limited: a seat can't create or sync profiles of its own
2. Share only the client profiles they need — a seat sees nothing you haven't handed it
3. Walk through one profile launch together — share screen, explain the proxy assignment, fingerprint settings, the works
4. Document the "never do this" list — no profile sharing outside the tool, no exporting cookies to personal browsers, no changing proxy assignments without approval
5. Review shared profiles weekly for the first month — who has been given what

Owners and admins get a 12-month team activity log with session durations. It isn't an audit log of every action, so keep your own record of who was given which profile. The structural control you do get is narrower than a log but harder to get wrong: a seat can't create profiles at all, so nothing turns up in your fleet that the subscription holder didn't make.

7. Can multiple people use the same profile simultaneously?

No.

Well, technically some tools allow it, but it's a terrible idea. Browser sessions aren't designed for concurrent access. If two operators open the same Facebook Business Manager profile simultaneously, one will get logged out, which can interrupt the work and may prompt an identity check from the platform. Your client's account is the one affected, so there is no reason to add the risk.

Treat profiles like physical computers: one person uses it at a time. Build your workflow around handoffs, not simultaneous access. Some agencies literally use a Slack bot to "check out" profiles and prevent collisions. Sounds overkill until you've dealt with the alternative.

8. What's the best folder structure for multi-client agencies?

What tends to work:

/Clients
  /ClientA
    /Facebook
    /Google
    /TikTok
  /ClientB
    /Facebook
    /Amazon
  /ClientC
    ...
/Internal
  /Testing
  /Sandbox

Platform-level folders under each client. Not the other way around. You want to answer "show me all of ClientA's profiles" instantly — not "show me all Facebook profiles" and then filter by client.

The /Internal folder matters more than you'd think. You need profiles for testing fingerprint configurations, proxy health checks, experimentation. Keep those separate from client work.

9. Should each client have their own proxy provider?

Depends on your risk model.

If a proxy provider's IP range gets blocked or rate-limited by a site, every profile using that provider is affected. Some agencies use one provider for all clients (cheaper, simpler), but that means a provider-level problem affects everyone.

The safer approach: at least two proxy providers in rotation, with different providers for your highest-value clients. If ClientA is 40% of your revenue, don't run them on the same $20/mo budget proxy as everyone else. Obvious? Maybe.

JustBrowser supports per-profile proxy assignment (HTTP/HTTPS/SOCKS5), so you can mix providers freely. Check our ISP proxy setup guide for the walkthrough.

10. How do we handle two-factor authentication across profiles?

This is operational, not technical. The browser doesn't solve 2FA for you — you need process.

Common options:

• Shared OTP app like 1Password Teams or Authy Multi-Device, where 2FA codes are accessible to whoever's working on that client
• Client-owned 2FA where the client keeps the authenticator and approves logins over Slack/call (annoying, but some enterprise clients require it)
• Hardware keys assigned to profiles — Yubikeys physically labeled by client, stored in a secure location

The worst approach: everyone texts the founder for 2FA codes. That doesn't scale past 5 clients.

11. Do team features work with the REST API?

The API belongs to the subscription, not to the seats. A free seat has no API access at all — no tokens, no endpoints. So if a contractor is writing automation against your profiles, they need their own subscription; there's no scoped key to hand them off yours.

That's a real constraint to design around, and it cuts both ways. If you're spinning up profiles via API (say, for Playwright or Puppeteer automation), keep the automation on the subscription that owns the profiles and let seats do the human work. And at $9.99, giving an automation engineer their own subscription isn't the budget conversation it used to be.

Not all tools draw the line in the same place. Some hand out one API key for the whole account regardless of who's holding it. Ask before assuming.

12. How do we prevent cookie leakage between clients?

Profile isolation handles this at the browser level — each JustBrowser profile is its own browser with its own cookies, localStorage, and indexedDB, and the same is true of most multi-account browsers.

But people cause cookie leakage, not browsers. The most common ways:

• Exporting cookies from one profile and importing into another (for "efficiency")
• Opening a client link in a personal browser that's logged into something else
• Copy-pasting session tokens between profiles

The fix is policy, not technology. Document it, train on it, audit for it. Some agencies have a "no cookie export" rule enforced through revoked permissions — operators can't use export features. Blunt, but effective.

13. Can agencies white-label multi-account browser access for clients?

Mostly no. JustBrowser doesn't have white-label client portals, and neither do most competitors.

Some agencies work around this by:

• Creating sub-accounts per client with limited permissions (effectively separate instances)
• Using screen share for client-facing profile work rather than giving clients login access
• Building custom dashboards that pull from the API and present a branded interface

That last option is real engineering work. If you're managing 100+ clients, a branded dashboard with read-only profile status might be worth the build. Maybe. Probably not for most shops.

14. What metrics should agencies track for profile health?

At minimum:

• Last login date per profile — so you know which client accounts have gone quiet
• Platform status — is the account live, restricted, or under review, and has the client been told?
• Proxy health — is the assigned proxy still working and in the right country?
• Configuration consistency — a periodic look at each profile's identity settings with a fingerprint checker, to catch accidental changes (background: JA4 TLS fingerprinting)

JustBrowser has real-time profile health scoring, which helps. But you still need a spreadsheet or dashboard tracking the client-level information (platform status, login frequency) that the browser can't know about. Annoying? Yes. Necessary? Also yes.

Pair with ClickzProtect if you're running ad campaigns — traffic quality issues often surface before they become account-level problems. For email outreach tied to your client work, JustEmails offers custom domain email hosting and a transactional email API.

15. How do operational risks differ for agencies versus solo operators?

Agencies have more moving parts. Here's why:

• More people, more variation in how work gets done. Different operators work differently, and handoffs between them are where mistakes happen.
• More profiles under one billing entity. If 500 profiles sit on a single subscription, one mistake in how they are managed can affect a lot of client work at once. That's a lot of eggs in one basket.
• More chance of proxy mix-ups. Solo operators with 20 profiles rarely assign the same proxy to two client accounts by accident. Agencies with 500 profiles and 3 people managing them? It happens, and it makes sessions inconsistent for the accounts involved.

Mitigation: tighter SOPs, regular reviews, separation of concerns. One person owns client onboarding, one person owns proxy management, nobody touches profiles outside their assigned folders. Bureaucratic? Sure. But it works.

16. How do we evaluate which multi-account browser to choose for a team?

Decision matrix that actually matters:

Where JustBrowser lands on that list: the native C++ Chromium engine (40+ identity parameters, patched on every upstream Chromium release), one plan at $9.99/mo covering unlimited profiles, and team seats are free and unlimited — with sharing as the access model, since a seat runs only what you've handed it. Flat pricing takes the top row of that table off the board entirely. That's our pitch. Take it or leave it.

Multilogin, GoLogin and AdsPower are established multi-account browsers with their own seat and profile pricing; check each one's published pricing page for current numbers. We're biased, obviously — compare what you're actually paying against what you're actually using.

Frequently Asked Questions

How much does multi-account browser team access cost per seat?

JustBrowser doesn't charge per seat at all — the one subscription is $9.99/month and team seats are free and unlimited. The trade-off is what a free seat can do: it runs profiles the team shares with it, but it can't create its own profiles, cloud-sync them, or use the REST API. So your real cost is one subscription per person who needs to build profiles, not one per person who touches them. Other multi-account browsers price seats and profiles differently, so check each one's published pricing page.

Can team members see each other's browser profiles?

Depends on permissions setup. Most multi-account browsers let you create shared profile pools visible to the whole team, plus private profiles per user. On JustBrowser, sharing is the permission model: a seat only runs the profiles you've shared with it, so juniors see their client work and nothing else.

What happens to profiles when a team member leaves?

Profiles stay with the account, not the person. On JustBrowser a seat never owns profiles in the first place — it can only run what the subscription holder shared with it — so offboarding is a permissions change rather than a recovery operation. Best practice either way: keep client profiles on the team account from day one, never in an individual's private setup.

How do agencies bill multi-account browser costs to clients?

Most agencies bundle it into their management fee rather than passing through itemized. If you have 50 clients and 200 profiles across a team of 5, you're looking at $9.99/mo when one person builds the profiles and the rest run them on free seats, or $49.95/mo if all five need their own subscriptions — somewhere between 20 cents and a dollar per client. Some agencies add a flat 'platform access' line item per client and keep the margin.

---

Try JustBrowser

Native Chromium multi-account browser for teams — not extension-based. Real C++ engine patches at the canvas / WebGL / audio / font / screen layer, so 40+ identity parameters are genuine, not faked. Local REST API + CDP for Playwright, Puppeteer, Selenium. $9.99/month or $99.99/year. 7-day free trial, card required — cancel any time in the seven days and you are not charged. Unlimited profiles.

Get started → · How it differs from Multilogin / GoLogin / AdsPower