Teamwork for the Afina antidetect browser

Teams are isolated workspaces — each one gets the accounts you hand to it. Each member has four permission toggles you flip on or off per their needs: Start/Stop profiles, Add accounts to team, Remove/Move accounts from team, Invite members. There are no preset roles — you compose what each person can do directly.

Sequentially, yes — anyone in the team with access can open and edit a shared profile. Two people running the same browser at once is not recommended (it would create cookie/session races), but the system doesn't hard-block it.

The old team loses access immediately — the profile disappears from their account list. The new team sees it as soon as you confirm the move. The operation is atomic.

No — Afina doesn't track user actions per se. What you do see are sync events on shared accounts: when a profile was updated, when auto-sync pulled data at start or pushed it back to the cloud at stop. This tells you an account is currently in use, without surveilling the team.

Owner revokes their team membership; the user instantly loses access to every account in that team and to the team-scoped encryption key. Cookies and credentials in shared accounts remain encrypted — leaving doesn't expose them.

Hybrid. Team membership and the list of accounts handed to each team live in the Afina cloud (so members on different machines see the same workspace). Account payloads — cookies, credentials, variables — stay encrypted with a team-scoped key the cloud can't read.