Home → Team members

Share browser profiles without sharing a login

The usual way teams handle this is one account and one password passed around. It works right up until someone leaves, and then every account you own needs its password changed. Members fix that: five people, five logins, and you decide what each one can reach.

Why a shared login goes wrong

One password for the whole team means everybody can reach everything. The freelancer hired for one client's Instagram accounts can open the profiles belonging to every other client. Nobody intends that; it is simply what a shared credential does.

It also makes leaving expensive. Revoking one person's access means changing the password, which means telling everyone else the new one, on the same day, and hoping nobody wrote the old one down. Most teams postpone that, which is the actual risk.

How members work

A member is a real account with its own email and password, created by you from the Members section. They install Parallel on their own machine, sign in with their own details, and see your workspace — but only the part of it you granted.

The profiles never belong to the member. They belong to the account that pays for them, which is what makes removing someone safe: there is nothing of theirs to orphan.

Granting access by group or profile

Access is given two ways, and they combine. Grant a group and the member sees every profile in it, including ones you add later — which is how most teams work, one group per client or per platform. Grant an individual profile for the cases that do not follow the grouping.

Profiles with no group are never shared automatically. Ungrouped is where a profile lands when nobody chooses, so treating it as shared would hand every newly created profile to the whole team. Those have to be granted one at a time, deliberately.

Members also only see the group names they were granted. The shape of the rest of your workspace stays private.

Read-only members

Each member is either able to edit or not. A read-only member can open and use every profile you gave them — launching a profile is a read, so nothing about their day changes — but cannot rename, reconfigure or delete anything, and their app cannot sync changes back over the team's work.

That is the right setting for anyone running accounts rather than managing them, which is most people you would add.

Removing someone

Deleting a member removes their login and nothing else. Their profiles, workflows and proxies stay exactly where they were, because they were always yours. The revoked login stops working immediately — not at the end of a session, and not once a token expires.

No password changes, no telling anyone else anything.

What it costs

Nothing extra. Five members are included on every paid plan, from Starter at $8/month upward. Several products in this category price seats separately on top of the plan; we do not, because a team of three running twenty-five profiles is a completely normal shape and charging twice for it is hard to justify.

Members are the one thing the free tier does not include — see pricing for the plans.

Setting it up

In the app, open Members in the sidebar. Add a member with their email and a password you choose, tick the groups or profiles they should reach, and decide whether they can edit. Share those sign-in details with them however you normally would.

They download Parallel, sign in, and their profiles are there — with the sessions already in them, since a profile's cookies travel with it rather than living on one machine.