All articles

Team, sharing and cloud sync

Work on the same profiles with your team, share single profiles with people outside it, and keep every profile's logins on all your computers — encrypted so that only you and your team can read them.

Members

Invite people by e-mail under Team (in the app or on the website). They accept with their own account; each member uses one seat of your plan.

The Team page: seats, invite, members with their role and profile access

The ⋯ next to a member: profile access, disable (keeps the seat, the member can't open the team until enabled again), sign out everywhere, send a password-reset e-mail, remove. Nobody else ever sees or sets a member's password.

Roles and permissions

RoleCan by default
OwnerEverything, always (can't be locked out)
ManagerEverything, including members and billing
MemberCreate, edit and open their profiles and the ones shared with them; proxies, cookies, automation, synchronizer, API

On Business and higher, Roles & permissions changes what Manager and Member can do and adds roles of your own, permission by permission — see all profiles, create, edit, delete, manage groups, see or change proxies, see passwords and 2FA, export and import cookies, export profiles, automation, synchronizer, team extensions, API, members, logs, billing.

Roles and permissions: a permission per row, a role per column

Which profiles a member sees

Without "See all profiles", a member sees the profiles they made, plus what was given to them:

  • Profile groups with view, open or edit access;
  • single profiles with the same three levels;
  • member groups: name a set of members once and give the whole set access to profile groups. The highest access wins.

Login security

Login security (Business and higher) sets rules for everyone except the owner. They apply right away, also to people already signed in:

Login security: required 2FA, allowed networks, approved computers, opening a profile on several computers

  • Members must use two-factor sign-in.
  • Allowed networks: IP addresses or ranges members may work from. Managers must keep their own address on the list.
  • Only approved computers: a member's computer asks for approval the first time it opens the team; approve it on the same page.
  • Several members may open the same profile at once. Off (the default), a profile opens on one computer at a time, so cookies are never overwritten. On, others can open it alongside — the app tells them who else has it open — and whoever closes it last saves the cookies and logins.

Share single profiles with another account

To let a client or a freelancer open a few profiles without joining your team, open a profile's menu (⋯) → Share with an account (or select several profiles and click Share with an account).

Share a profile: their e-mail address, "Can open" or "Can see", and who has it

  • The other person keeps their own account and accepts by e-mail. Your workspace then appears in their workspace list as shared with you, with only the profiles you shared.
  • A guest uses no seat and has no team permissions: they can see or open what you shared, but not edit, delete, export or see your proxies and other profiles.
  • Up to 25 people outside the team. Stop sharing takes a profile back; when their last profile is taken back, the guest leaves your workspace.
  • Sharing needs the "Manage members" permission.

Transfer… in the same menu is different: it hands the profile over to the other account for good, with its proxy, tags and encrypted cookies.

Cloud sync

When a profile closes, the app encrypts its browser data on your computer (AES-256-GCM) and uploads only the ciphertext. When the profile opens on another computer, the latest copy is downloaded and decrypted there.

  • The server stores only ciphertext and never has your keys.
  • Logins come along. On Windows the browser locks cookies and saved passwords to the computer they were made on; from version 1.8.3 the app takes that lock's key along (inside the same encryption) and hands it to the browser on the other computer. A profile last saved by an older version brings its logins after you open and close it once with 1.8.3 on the computer that used it last.
  • What is kept can be chosen per profile: cookies, local storage, IndexedDB, history, bookmarks, saved passwords, extensions and open tabs (editor → Advanced).
  • The last few copies are kept per profile; how many depends on the plan.

If saving was interrupted. When the app is closed, crashes or loses its connection while a profile is being saved, it finishes the upload the next time it starts (and every few minutes while it runs). If someone opened the profile on another computer in the meantime, their newer version is used and your computer keeps its own copy and tells you: profile menu (⋯) → Restore this device's copy brings it back (the version it replaces is kept the same way, so you can switch back).

Keys. Each person has a key pair. The private key is protected by your sync passphrase and kept in your system's keychain on each computer. The team's key is shared with each member by encrypting it to their own key. Forgetting the passphrase means starting with a new key: synced data made with the old one can't be read any more.

Profile locks

While a profile is open on one computer it is locked everywhere else (unless your team allows opening it on several computers, above). Locks end by themselves when a computer goes offline, and people with edit access can force-unlock a profile from its row.

If your computer slept or was offline long enough for the lock to end and someone opened the profile elsewhere, the app tells you when it wakes up. Close the profile on one of the two computers, so the two copies don't overwrite each other's cookies and logins.

The activity log

Logs shows what the team did — profiles, proxies, members, automation and billing — with who did it, when and from which computer, filtered by area, member and date, and exportable. The sign-in history of members is there too.