Let me ask you something uncomfortable: how many of your VA's devices right now have your clients' Instagram passwords saved in them?

If the answer is "most of them," you have a problem you're not thinking about. Every password you share is an account you don't fully control anymore. The VA logs in from their home IP in a different city, Instagram sees a login from an unrecognized location on an unrecognized device, and your client's account eats a security flag. Or the VA leaves, and you're changing thirty passwords on a Friday night.

There's a better way. Here's my handover SOP.

Why passwords are the wrong tool

Passwords were designed for one human owning one account. Agencies break that model completely: five team members, thirty client accounts, constant handovers. Every shared password creates three risks — location mismatch (VA's IP vs client's city), device mismatch (VA's laptop fingerprint vs the usual one), and access sprawl (ex-VAs who still have the password in their notes app).

The fix: stop sharing credentials entirely. Share profiles instead.

The SOP: handing a client to your VA

  • Step 1 — Client lives in one isolated profile. Every client account already has its own browser profile in BeastBrowser — own fingerprint, own proxy matched to the client's city, own timezone. This is the unit of handover. Not the password. The profile.
  • Step 2 — Give your VA a team seat with a role. Add the VA to your team with a scoped role: access to their clients' profiles only, not the whole roster. Your premium clients' profiles stay invisible to junior VAs. Roles also mean you can revoke one person's access in ten seconds without touching anyone else.
  • Step 3 — The VA opens the profile, never the password. The VA clicks the client's profile and they're logged in — the session, the proxy, the fingerprint all travel with the profile. They never see, type, or store a password. Their home IP never touches the client's account because the profile's proxy handles the connection.
  • Step 4 — 2FA stays with you. Keep two-factor authentication codes on your device or your password manager, not the VA's. If a login challenge ever appears, you approve it — the VA never needs the keys to the kingdom.
  • Step 5 — Written handover checklist per client. Every handover gets a one-page doc: content calendar link, posting cadence, tone notes, what's off-limits, who approves what. The profile handles the technical side; the doc handles the human side.
  • Step 6 — Offboarding in one click. VA leaves? Remove their seat. Every profile they touched stays exactly as it was — sessions intact, no passwords to rotate, no 2AM panic. This alone is worth the whole system.

What this costs vs. what it saves

Team seats cost money — check pricing for current plans. Now compare that to one banned client account: the refund you owe, the replacement cost of rebuilding the account, and the client who tells three friends your agency got their account killed. The math isn't close.

I also keep an audit habit: once a month I review who has access to what. Five minutes, catches everything — the VA who kept access to a client they stopped working on three months ago, the role that's broader than it needs to be.

Tell the client what you're doing (they'll love it)

Most agencies hide their operational setup from clients. Don't. I tell every new client, in plain language: "Your accounts live in their own isolated, secure profile. Nobody on my team ever sees your password, and if someone leaves, their access disappears instantly." Clients love hearing this — it sounds like enterprise security because it basically is. Twice now, this exact paragraph has won me a client over a cheaper competitor. Security isn't just protection; it's a sales asset. Put it in your proposal template.

The honest question

Right now: do you hand your VA the client's password, or do you share the profile? Be honest in the comments. No judgment — half the agencies I talk to are still on passwords. But if you're on passwords, this SOP is your upgrade path, and your future self will thank you.