Running client accounts at an agency without shared passwords
Agencies run accounts for many clients at once: ad accounts, social profiles, marketplace seller centers, analytics. The work itself is ordinary. What goes wrong is usually the setup around it: one browser with fifteen logins, a shared password sheet, and a teammate who leaves with access nobody remembers giving.
This guide is a practical way to organise that work so every client stays separate, every teammate has exactly the access they need, and handing an account back is one click.
Give every client its own space
Start with structure, not tools:
- One profile per account. A profile is a separate browser with its own cookies, logins, extensions and fingerprint. A client's ad account and its Instagram are two profiles, not two tabs.
- One group per client. Groups such as Client A · Shop or Client B · Social keep the list readable and are the unit you give access to.
- Tags for the rest: the platform (
meta,google-ads), the state (warming,review), the market (us,de). - Notes on the profile for what anyone opening it needs to know: who at the client approves spend, which payment method is on file, which two-factor method is used.
With this in place, "who can open Client A's accounts?" has a one-line answer: whoever has access to the Client A group.
Match each account's network to its market
Platforms look at where an account is used from. An account created in Germany and suddenly managed from another continent every morning looks odd, even when the reason is innocent.
- Give each client's profiles a proxy in the client's own market, and keep it stable over time. Changing a profile's country every week is a bigger signal than any single location.
- Let the profile's time zone, language and location follow the proxy (on by default), so the browser doesn't say "Dhaka" while the IP says "Berlin".
- Don't share one exit IP between unrelated clients. If one client's account is reviewed, the others shouldn't be pulled in with it.
Before going live, run a leak check on each profile: it confirms that sites see only the proxy — no real IP through WebRTC, DNS or forwarding headers.
Access: least privilege, by default
Agency teams change. Contractors come and go, a client's in-house person needs to see one account, a junior should run campaigns but not export cookies.
- Roles decide what someone can do: a Member opens and edits their profiles; a Manager also manages people and billing. On Business plans you can make your own roles, permission by permission — for example "Campaign runner": open and edit profiles, no password viewing, no exports.
- Access decides which profiles they see: per group, or per single profile, as view, open or edit.
- Login security can require two-factor sign-in for everyone, limit work to your office's networks, and require that a manager approves each new computer.
When someone leaves, remove them from the team: their access, their computers' approval and their copy of the team's sync key go with them, and profiles they had open are released. (Before removing them, Sign out everywhere in their member menu also ends the sessions on their own devices.)
Share one account with the client, without the rest
Clients sometimes want to log in themselves — to approve an invoice or check a report. Instead of giving them a password:
- Open the profile's menu and choose Share with an account.
- Enter the client's e-mail address and choose Can open.
They keep their own account and see only what you shared, in a workspace marked shared with you. They use no seat on your plan and can't edit, export or see your other profiles and proxies. When the job is done, Stop sharing takes the profile back.
If the client takes the account over for good, Transfer hands the profile to their account — with its proxy, tags and encrypted cookies — so nobody has to log in from scratch.
Keep logins where they belong
Cookies are the account. Two habits keep them safe:
- Cloud sync is end-to-end encrypted. A profile's data is encrypted on the computer before it is uploaded; the server only stores ciphertext. Any teammate with access opens the profile already logged in, on their own computer.
- One computer at a time. While a profile is open on one computer, it is locked for everyone else, so two people never overwrite each other's session. (Teams that really need several people in one account at once can allow it in Login security.)
Avoid exporting cookie files unless you have to. If you do, treat the file like a password and delete it afterwards.
Repetitive work: let the app do it
The tasks that eat an agency's week are the same steps across many accounts:
- Batch create new client profiles with proxies handed out one per profile, or import them from the spreadsheet you already keep.
- Bulk edits: move twenty profiles to a new group, give them new proxies, add a tag — in one go.
- The synchronizer repeats what you do in one window in all the others, for checks you'd otherwise click through fifteen times.
- Automation flows run steps like a person would, on a schedule, without code.
Keep automation within each platform's rules. If a platform doesn't allow automated actions for a task, do that task by hand.
A short checklist
- One profile per account, one group per client, notes on every profile.
- A stable proxy in the client's market; time zone and language follow it.
- A leak check before a profile goes live.
- Roles and group access instead of shared passwords; two-factor sign-in required.
- Share or transfer single profiles to clients instead of sending logins.
- Remove people the day they leave.
Only manage accounts you own or are authorized to manage, and follow each platform's terms. Our Acceptable Use Policy has the details.