Team workspaces: share browser profiles without sharing passwords

One person running fifty profiles is a workflow. Three people running the same fifty profiles is usually a spreadsheet of passwords, a shared proxy login pasted into a chat, and nobody sure who changed what. Teams in the AntiBrow desktop app replace that with grants: you decide which profiles a teammate can see, and what they are allowed to do with them.

What a team is

Every paid account has a team. There is nothing to create: open Team in the sidebar, give it a name if you like, and add people by the email they signed up with. A teammate can be any registered AntiBrow account, including a free one. They do not need their own plan to use what you share with them; the profiles stay yours and count against your plan.

Teams are loose on purpose. There are no roles to configure and no invitations to accept. You add someone, and from then on they see exactly what you grant them, nothing else.

Two ways to share

A whole group. On the Team page, pick a teammate and grant one or more of your groups. The grant follows the group, not a fixed list: a profile you move into the group later shows up for them automatically, and a profile you move out disappears from their list. This is the right tool for "the EU accounts are Anna's".

A single profile. Open a profile's Edit dialog and go to the Members tab. Every teammate is listed with a permission picker. Use this for the one-off: a profile someone needs for a day, or one that does not belong to any group.

Only cloud-synced profiles can be shared, since the teammate's computer has to fetch them from somewhere. A local-only profile needs to be synced first.

Three permission levels

• Read: the teammate can open and use the profile. They cannot open its edit dialog.
• Edit: they can also change the name, note, tags and the advanced switches.
• Delete: they can also delete the profile. Deleting removes it for you and for everyone else it was shared with, so grant this one sparingly.

Some things stay yours whatever the level: the proxy, the group, the browser core version and the device identity. A teammate changing any of those would quietly change the profile under your feet, so the server ignores those fields when they come from anyone but the owner.

If a profile reaches someone through more than one grant, for example Read through a group and Delete on the profile itself, the highest level applies.

What your teammate sees

On their side, the profile list opens on Mine, their own profiles. A view switcher next to it lists All and one entry per team they belong to, so shared profiles never mix into their own list by accident. Team rows carry the team name as a badge, and the proxy column reads Owner's proxy.

When they open a shared profile, it starts with your fingerprint, your cookies and logins, and your proxy. That includes proxies you added yourself, not only managed ones: the profile only behaves like the same browser if it leaves through the same connection. Add people you trust with that connection. Whatever they do in the browser is saved back to the cloud when they close it, so you see the same session state next time you open it.

One limit worth knowing: if two people have the same profile open at the same time, whoever closes it last is what gets saved. Agree on who is using what.

Taking access back

Remove a teammate on the Team page, drop a group from their grants, take them off a profile's Members tab, or move the profile out of a shared group. Each of these takes effect on the server immediately: the profile disappears from their list on the next sync, their app deletes its local copy, and the proxy credentials it was using stop working. A teammate can also leave a team themselves from the same page.

If your plan lapses, shared profiles stop being available to your team. Nothing is deleted: renew and every grant comes back as it was.

One computer, several accounts

Shared machines raised a second problem. Until now the desktop app kept one local list per computer, so signing in with a different account showed the previous account's profiles as if they were your own. Since version 1.16.0, local data is kept per account: each account sees only its own profiles, proxies and sync state, and switching back brings everything back. If you are updating a computer that has been used with more than one account, existing profiles are handed to the account that actually owns them the first time that account signs in.

Getting started

Update the desktop app to 1.16.0 or newer, open Team, add a teammate's email, and grant a group. They will see it the next time their app syncs.