A teammate opens the profile and is already signed in, on the same cookies, the same fingerprint and the same proxy. You choose which groups of profiles they see and what they may do with them, person by person. Take them off the team and everything they were given goes back, that minute.
Start freeFour moments when a shared login goes wrong, and the same four with a shared profile.
Two settings decide what a member can touch, and you set them separately: which profiles they see, and what they may do to them.
Give a member one profile group or several. They see every profile in those groups, including the ones you create next month. Leave the box empty and they see nothing at all. Tick See all profiles and the groups stop mattering.
Being given a group is what lets someone open and run those profiles. There is no separate tick for that, because the scope is the access.
Four switches, each one off until you turn it on. On your own data you keep all four, whatever you grant.
| Permission | What it covers |
|---|---|
| Create profiles | New profiles belong to you and use a seat from your plan. |
| Edit profiles | Name, note, group, tags, proxy and fingerprint. |
| Delete profiles | Deletes for good, including your own copy. Leave this off unless you mean it. |
| Manage proxies | View, add, edit and delete proxies. |
Two people on one team rarely do the same job. One way a team of three ends up set up:
| Permission | Ad buyer | Account farmer | Operations lead |
|---|---|---|---|
| Profile groups they see | Ads | Farm, Warmup | See all profiles |
| Create profiles | |||
| Edit profiles | |||
| Delete profiles | |||
| Manage proxies |
Nothing in that table is a preset. Every switch is set on one member, and changing it leaves everyone else alone.
Two routes, and you open both of them deliberately.
Open the profile menu, choose Share, and type the email of any SigoLogin account. Only that profile travels. The email does not need an account yet: the invitation waits and attaches the first time they sign in.
There are no permission switches outside a team. Someone you share with one-to-one uses the profile in full, but cannot edit it and cannot delete it. The four switches apply to team members only.
The second is your team: assign a group to a member on the Team page and EVERY profile in that group travels, including ones you create later. Tick "See all profiles" for someone and all of your profiles travel. Your app uploads them by itself at its next sync, with nothing to click. A profile in no group assigned to anyone is never packed up and sent.
You run the team from the Team page on this site or from the Team screen in the app, whichever is in front of you. Both write to the same list.
Opening a shared profile takes a lock that lives 300 seconds, and the app renews it every 100 seconds while the browser is open. Anyone else who opens the profile sees the email of the person holding it, and you can take the lock back from them.
Stop sharing and the browser on the other side closes by itself, within 100 seconds at the worst.
When a session ends, whoever held the lock uploads a fresh bundle, so the next person to open the profile finds the cookies as they were left. That includes you: the owner downloads the bundle like everybody else.
Remove them from the team and every profile they were granted is revoked. It takes effect immediately, and no account password has to change for it to hold.
Hand a profile to a colleague with its cookies and signed-in state intact. They open it and start working, with no second login and no password sent over chat.
From the Team page on this site, or the Team screen in the app. They do not need a SigoLogin account yet.
Name the profile groups they see, or tick See all profiles. Then turn on what they may do. Everything starts off.
Your app packs the profiles and uploads them at its next sync. They show up on the other machine already signed in, on the same proxy and the same fingerprint.
A profile stays in a folder on your disk unless you share it. Sharing is the exception, and it has to be: the person opening it sits at another machine, so the cookies, the proxy and the saved accounts have to travel.
The bundle carries the profile name and note, the fingerprint, the proxy including its password, the cookies, and the accounts you saved next to the profile including passwords and 2FA keys. Leave any of those out and the person you shared with cannot actually use the profile.
The bundle is encrypted with AES-256-GCM while stored on our server. The key lives in our server configuration, so to be plain about it: this is encryption at rest, not end-to-end encryption, and we are technically able to read the bundle.
When nobody can see it any more, the bundle is deleted. Removing the last person, taking a member out of a group, or moving the profile to a group nobody is assigned to all end the same way. We keep no copy.
A plan's team size includes you. Professional is a team of three, which means you and two other people.
| Feature | Free | Personal | Professional | Business |
|---|---|---|---|---|
| Team size, counting you | 1 | 1 | 3 | Unlimited |
| Share your profiles out | ||||
| Receive a profile someone shares with you |
Receiving works on every plan, Free included, and a profile shared with you does not use one of your own profile slots. Sharing profiles out is the part that needs Professional or above.
Need more people than the plan carries? Seats are sold one at a time on top of it: $0.99 per person per month.
Remove them from your team. Every profile they were granted is revoked immediately, their copy goes the next time their app syncs, and you change no account passwords.
No. Opening it takes a lock of 300 seconds that the app renews every 100 seconds. Everyone else sees the email of the person holding it, and the account owner can take it back.
No. Every plan can receive a shared profile, Free included, and it does not use one of their own profile slots. Sharing profiles out is what needs Professional or above.
On your machine, unless you share the profile or give a team member its group. Then a bundle with its cookies goes to our server, which stores it encrypted with AES-256-GCM under a key we hold.
Not outside a team. A one-to-one share gives full use of the profile but no editing and no deleting. The four permission switches apply to members of your team only.
Not in this build. You can see who is holding a profile right now, by the email shown on it, but nothing keeps a history yet.
The free plan gives you three profiles and takes whatever anyone shares with you. Sharing your own profiles out starts on Professional.
