Multi-Account Browser for Canva and Figma Agency Teams: Seats and Rules

Picture a studio designer on a Thursday afternoon: three Figma files for three clients, two Canva brand kits, and a Google sign-in prompt asking which of four accounts they meant. They pick the wrong one. Client B's logo lands in Client A's social template, and nobody notices until Client A does. A multi-account browser can stop exactly that, and in a design agency it's the strongest reason to run one.

Because the real problem agencies have with design tools isn't bans. It's mix-ups.

People sometimes look for a browser tool to solve something else entirely: one shared seat used by several designers. That is the wrong job for it on two counts. It breaks both platforms' terms, and it fixes something most agencies don't actually suffer from. Canva and Figma are built for one person working across several teams. What gets agencies into trouble is several people sharing one login.

So here's what the platforms allow, why they push back on shared seats, and where a separate browser profile, including a multi-account browser like JustBrowser, actually earns its place.

What Canva and Figma already let you do

Start here, because plenty of agencies build workarounds for things the tools already handle.

Figma lets one account belong to more than one team, and its organization plans let admins invite people from outside the company as guests. There's also an account switcher, so a designer with an agency login and a client-issued login can be signed into both and flip between them without logging out. Paid plans bill per seat, and the team or organization that adds you decides what kind of seat you get and who pays for it.

Canva lets one person be a member of several teams and switch between them from the account menu. Brand kits, templates and folders live with the team, so Client A's fonts and colours sit in Client A's team, not in yours.

Put those together and the normal agency setup is almost boring:

• Each designer has their own login.
• Each client invites that designer into their workspace, or the designer works in an agency-owned team and hands the files over at the end.
• Whoever owns the workspace pays for the seat.

No fingerprint tricks anywhere in that list.

One caveat, and it's an irritating one: both companies have renamed plans, reshuffled seat types and revised guest rules more than once, so anything you write down about them has a short shelf life. Check their current pricing and help pages before a word of it goes into a client contract. Don't take a blog post's word for it, this one included.

Why the platforms push back on shared logins

Both companies sell per person. A seat is a named user. When five designers share one paid login, that's four seats nobody paid for, and both companies' terms tie an account to an individual. Read the current wording on their legal pages rather than treating this summary as the final word.

But licensing is only half of it, and honestly the less interesting half. A shared login is the worst habit in agency operations, and the reason has nothing to do with anyone's terms:

• Nobody can tell who changed a file, because every edit carries the same name.
• Two-factor authentication stops doing its job. Either the code goes to one person's phone and the whole team pings them for it, or someone switches 2FA off so everyone can get in.
• When a designer leaves, the only way to cut them off is to change the password on everyone else.

Platforms also watch for the patterns sharing leaves behind: one account active in several places at once, sign-ins from new devices and new locations in quick succession, a session that hops between cities faster than any person could travel. Some of that is licence enforcement. A lot of it is the same account-takeover protection your bank runs.

The two are hard to tell apart, which is one more reason to give every designer a real seat and a real login.

What working around it actually costs

Some agencies are tempted to stretch one paid seat across several people. Here's the honest bill.

It's a terms violation. Sharing one seat doesn't make it several seats, however the sessions are arranged. When it's found, the usual outcome is a restricted or closed account, and the files go with it.

It's often the client's account on the line, not yours. If the shared seat lives in the client's workspace, you've put their workspace and their design history at risk to save the cost of a few seats. That's a very awkward call to make.

It can breach your own contract. Plenty of agency agreements include a clause about complying with third-party software licences. Check yours. Don't assume it's silent.

It doesn't save much. Per-seat pricing adds up across a big team, sure. It's still small next to a lost retainer or a frozen workspace in the middle of a launch. Put the seats on the client's invoice. And if a client refuses to pay for one seat per designer, that's a scoping conversation about what the retainer covers, not a browser problem — our view is you have the conversation, awkward as it is, because the alternative is carrying their licence risk for free.

If a workspace has already been restricted, the way back is the official one, covered further down.

Who pays for the seat: three setups that hold up

The third is where things get messy. A designer can end up with an agency Google Workspace account, a client-issued Microsoft 365 login and a second client's Okta sign-in, all needed for the same two design tools on the same afternoon.

Which brings us to the part where a browser profile genuinely helps.

Where a separate browser profile genuinely helps

Here's a slightly unpopular take from a company that sells a multi-account browser: for a freelancer with two or three clients, you don't need one for this job. Figma's account switcher and Canva's team switcher are enough. And the identity-parameter side, which is a big part of the engine (canvas, WebGL, audio, fonts and screen are all patched in C++), barely matters for design work at all. A designer can leave that screen alone.

What does matter, once you're past a handful of clients, is session separation:

• SSO collisions. Sign into Client A's identity provider in the same browser as Client B's, and the next "Sign in with Google" or "Sign in with Microsoft" button grabs whichever session it finds first. That's how Client B's logo ends up in Client A's file.
• Saved passwords and autofill. One browser, thirty client logins, one autofill dropdown. It goes wrong eventually.
• Extensions. A client's security team may not love your agency's collection of extensions running inside their workspace. A clean profile per client keeps them out.
• Downloads. Exports from every client pile into one Downloads folder, and that's exactly where the wrong file gets attached to the wrong email.

Separate Chrome profiles get you part of the way, and we compare the options in multi-account browser vs incognito vs separate profiles. Where a multi-account browser's profile manager pulls ahead is the team side: giving the right person access to the right client profile, controlling who can launch what, and keeping forty profiles organised instead of four. Separate profiles are also how app teams QA in-app review prompts without touching their public listing, if that's on your plate too.

Setting up multi-account browser profiles in JustBrowser, the clean way

This workflow assumes every designer has their own seat in every client workspace they touch. If that isn't true yet, fix that first. Nothing below replaces it.

1. One profile per person per client. Name it so the owner is obvious, like ACME-FIGMA-RACHEL or GAMMA-CANVA-MARCUS. The person's name in the label is a reminder that the login inside belongs to exactly one human. Write the convention down somewhere, too. Ad-hoc naming tends to fall apart somewhere around the ninth profile, when "acme-2" starts meaning two different things depending on which week it was made.

2. Sign in with that person's own seat. The profile holds the session. The session belongs to the designer named on the profile. Never put a login into a profile so that several people can use it.

3. Leave the fingerprint on its defaults. JustBrowser generates a consistent identity for each profile from its engine (40+ parameters covering canvas, WebGL, audio, fonts and screen). For design work there's no reason to touch any of it. If you're curious what those parameters are, our piece on browser fingerprinting covers it, and the TLS fingerprint explainer goes a layer lower. Neither is required reading for a designer.

4. Skip the proxy unless the client requires one. Figma and Canva don't need one. The only good reason to send a client profile through a particular network is that client's own policy. If their IT says work goes through their VPN or a fixed address, use what they give you. That's what per-profile proxy settings are for here.

5. Share profiles, not sessions. JustBrowser's team seats are free, and a profile can be shared with view-only or launch permission. For an agency, the clean pattern is that whoever holds the subscription creates each designer's client profiles and shares each one with that designer only. A free seat can launch profiles shared with it, but it can't create or sync its own profiles or use the API, so that division of labour fits the product. What you don't do is share a profile that has someone else's Figma session in it. That's the shared-login problem again, with extra steps.

Handy detail: a synced profile runs on one device at a time, which suits a one-profile-per-seat setup.

6. Offboard through the client, not the browser. When a designer moves off an account, the client's admin removes their seat (or you do, if it's your team). Then delete the profile. The replacement designer gets their own invite and their own profile, not the old one with someone else's session still inside.

7. Automate the boring part, if you like. JustBrowser's REST API runs locally, so a morning script can open each designer's client profiles in turn; our REST API tutorial walks through it. One gotcha: the API starts profiles headless unless you send {"headless": false}. A designer who runs the script and sees nothing happen hasn't broken anything, they've just hit that default. Send the flag. Free team seats have no API access, so the script runs under the subscribed account. More agency-specific questions are covered in our teams and agencies FAQ.

On cost, it's one plan: $9.99 a month or $99.99 a year, unlimited profiles, free team seats.

Check your hardware before you standardise on any of this, though. JustBrowser runs on Windows x64 and on Apple Silicon Macs. No Linux build, no mobile app. If half your studio is still on older Intel Macs, that's a hard stop rather than an inconvenience, and it's far better to find that out today than on the morning you've told six designers to install something.

If a client workspace gets locked or flagged

It's usually for duller reasons than people assume. Work through it in this order.

1. Read the notice properly. "Unusual sign-in detected" and "your seat was removed by an admin" are completely different problems with completely different fixes.
2. Talk to the workspace owner. In a client's workspace, the client's admin controls seats and guests. A lot of "lockouts" turn out to be an expired invite or a seat that got downgraded during a billing change.
3. Use the official support route. Figma and Canva both run help centres with a way to contact support. For an organization or enterprise workspace, go through the client's admin, who usually gets a faster answer than an outside guest would.
4. Secure the account. Reset the password, check 2FA and review active sessions. If the trigger was a sign-in nobody on your team recognises, treat it as a security incident before anything else.
5. Don't route around it. Canva's terms bar a new account after a termination for a violation unless Canva gives written permission. Figma's acceptable use policy forbids sharing credentials and misrepresenting who you are. Check each company's current terms, but either way, a new account or a new email to get back into the same workspace breaks the rules, and it tends to turn a temporary restriction into a permanent one.

If the restriction came from several people sharing one login, the fix is more seats. Annoying to pay for. Far cheaper than the alternative.

Frequently Asked Questions

Can one designer work in several clients' Figma and Canva workspaces?

Yes, in the normal case. Both tools are built for one person belonging to several teams: Figma lets an account join multiple teams and organizations can invite outside guests, and Canva lets you switch between the teams you belong to. Being a member of many workspaces isn't what the platforms push back on. Several people sharing one login is.

Is it against Canva's or Figma's terms to share one paid seat among several designers?

Both companies sell seats per person and their terms tie an account to an individual, so sharing one login across a team is a terms problem. Making the shared login look like several unrelated users doesn't turn it into several seats. Read the current wording on each company's legal pages, and bill the extra seats to the client if the work is theirs.

Do I need a multi-account browser for agency design work?

Not for compliance, and not if you only have two or three clients. Figma's account switcher and Canva's team switcher cover that. A dedicated profile manager starts to earn its place when designers juggle several client sign-ins, SSO identities, password managers and extensions, and you want each client's sessions kept apart and shareable with the right teammate.

Do I need proxies to use Figma or Canva across client workspaces?

No. Design tools don't need them. The only good reason to route a client profile through a particular network is the client's own policy, such as a requirement to work through their VPN, and then you use exactly what their IT team gives you.

What should I do if a client's Figma or Canva workspace gets restricted?

Read the notice carefully, then talk to the workspace owner, because the client's admin controls seats and guests and many lockouts are an expired invite or a changed seat. Use the official support route in each tool's help centre, secure the account if the trigger was a sign-in you don't recognise, and don't create a new account or a new identity to get back in.

---

Try JustBrowser

A multi-account browser for teams, built on a custom Chromium engine with native C++ integration, not an extension. Real C++ engine patches at the canvas / WebGL / audio / font / screen layer, across 40+ identity parameters. Each profile keeps its own cookies, storage and proxy, and teammates can share profiles. Local REST API for Playwright, Puppeteer and 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, unlimited cloud sync, unlimited team seats.

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