How agencies manage multiple client browser profiles

One profile per client account

The rule that prevents the worst mistakes is simple: one browser profile per client account, never shared with another client. It stops the wrong analytics property loading, the wrong ad account being charged and the wrong post going out. Everything below assumes that rule is already in place.

Naming and colour conventions

• Profile name: client code first, then the account type — “ACME — Ads”, “ACME — Analytics”.
• A distinct profile colour per client, reused by everyone on the team.
• Bookmark folders prefixed with the same client code so trees sort identically for everyone.

Consistency here is what makes a new team member productive on day two rather than week two.

The internal toolkit folder

Every profile needs the same small set of internal links: the project tracker, brand assets, process docs, the reporting template, the status page. Rebuilding it per profile is wasted time and it is always out of date somewhere.

Maintain it once and share it into every profile with cross-profile bookmark syncing. When a tool is replaced, you update one folder and the change lands everywhere, including the removal of the old link.

Campaign tab groups

For a launch or an audit, a named tab group holding the dashboards, briefs and trackers is more useful than a folder, because it restores a working context rather than a list. Share the group to the profiles working that campaign and it arrives collapsed — tab group syncing covers the behaviour.

Onboarding and offboarding

1. New client: create the profile, apply the naming convention, receive the toolkit folder automatically.
2. New team member: install the extension in their profiles, activate their seat, toolkit arrives.
3. Client ends: delete the client profile. Nothing shared was client-specific, so nothing else changes.
4. Team member leaves: revoke their seat; their local profiles stop receiving updates.

What must never be shared

• Client-specific folders — they belong in the client profile only.
• Anything account-scoped that would error under another identity anyway.
• Credentials of any kind. Braid Sync never transmits cookies, sessions or passwords; use a password manager with proper per-client vaults for access.

The data boundary is documented on the security page — worth reading before rolling anything out to a team, and worth forwarding if a client asks what is installed in their profile.