Antidetect browser team management
Antidetect browser team management assigns browser profiles for multiple accounts to the people responsible for them. WGBrowser provides member roles, group access, operation permissions, and profile occupancy information. Team members use assigned profiles on their own computers with the corresponding account details, proxy, and browsing data.
Start by organizing profiles around clients, stores, or platforms. Then give each member the relevant groups and permissions for their work. For daily handoffs, check the profile name and current user, close it on the original device, and let sync finish before the next member opens it.
Members, roles, and permissions
Administrators can create members, set roles, and assign profile access in the web console. The roles are owner, admin, and member. Group access determines which profiles a member can see. Separate permissions cover creating, editing, deleting, and exporting profiles, managing proxies and scripts, running automation, and using the Local API.
Match permissions to responsibilities. Someone operating a set of client accounts needs the relevant groups; the person maintaining proxies also needs the applicable proxy management permission. Seeing a profile does not grant every management action. The application checks the permission required for each operation.
The client uses labels such as Create profiles, Edit profiles, Export profiles, Manage proxies, Run automation, and Use the Local API. Profile, member, and cloud storage capacity depend on the plan. Check plans and pricing before adding staff or increasing the number of profiles, then verify each member's assigned groups.
Organize profiles by client, store, or platform
Use the group bar on the Profiles page to organize profiles, including dragging a profile into a group. Give each profile a name, tags, and notes that identify its purpose. Keep the platform account information attached to the corresponding profile so a teammate can find the correct account before opening it.
If a client has several stores, keep each store in its own profile with its own proxy assignment. A member responsible for several accounts opens the relevant profile for each account. Groups organize access; the fingerprint settings, cookies, and proxy configuration are stored per profile.
Before changing responsibilities, list the profiles and work being handed over, then update group access. A platform login and a team member's client login serve different purposes. For examples of account organization, see Amazon store management and Google Ads account management.
Profile occupancy and shift handoffs
Opening a profile acquires its occupancy lease. Only one device can use that same profile at a time. A member who tries to open an occupied profile can see the current user's device and timing information. Owners and admins can use Take over, but routine handoffs should start with the current user closing the profile normally.
Closing also uploads the selected storage snapshot. With the required sync options enabled and uploads complete, the next member opens the same profile with updated cookies and selected storage. The cloud sync guide explains the different timing for cookies, tabs, LocalStorage, and IndexedDB.
Occupancy shows who is using the browser profile; it does not confirm that a website operation has finished. After taking over the work, check the account identity, website sign-in state, and proxy exit IP. If the website asks for verification again, complete its requested steps.
- Confirm which profile and account the next member will use, and check that their group access includes it.
- Finish the current operation, close the profile on the original device, and wait for sync to complete.
- Open the same profile on the next member's device and verify the website before continuing.
Saved passwords and platform 2FA
The password manager offers saved logins from a website's sign-in field and lets you save credentials after signing in. Those saved logins stay with the profile for team use. A profile can also hold its platform username, password, and 2FA secret, with the current verification code available when signing in.
Platform credentials and saved website passwords are separate data types. Sharing and exporting have separate content controls for them. Before handing a profile to another team, decide whether the recipient needs Passwords and 2FA, Saved site passwords, or both. Check the password manager for how these records relate to each profile.
An AI assistant can use the MCP credential-filling tool to put a stored login into a page without that tool returning the username or password. MCP tool visibility and sensitive-data settings have their own controls. Read the MCP guide alongside the team's permissions when configuring assistant access.
Plugin visibility and local runs
A plugin's Visibility can be All team members, Only me, or Selected members. Owners and admins can always view and manage all team plugins. The uploader can change who sees their plugin; another member with management permission may update a visible plugin without gaining permission to change its visibility.
A plugin outside a member's visible scope does not appear in that member's plugin list, MCP tools, or Local API. Share a common workflow with the team or limit a client's workflow to its assigned members. The member still needs access to the profiles selected for the run.
A team plugin needs approval the first time it runs on a member's device. Changed plugin content may require approval again. Run records remain on the computer that started the task, so check that device when reviewing a run. The automation guide covers installation, parameters, and retrying work.
Recycle bin and transfers to another team
When the plan includes the recycle bin, deleted profiles go there first and can be restored. Check whether the profile is still needed, whether a backup is required, and what the deletion prompt says. Without the recycle bin feature, do not assume a deleted profile can be recovered in the same way.
For a new person taking responsibility inside the same team, updating group access usually keeps everyone working with the original profile. To give another team or client an independent copy, use a share code or export a .fgbx file with the required permissions. Profile sharing explains content choices and recipient limits.
The recipient manages a claimed copy separately. Revoking the code only stops future claims and does not recall copies already received. Review the contents, expiry, and claim history for an external handoff, then confirm that the recipient received the intended profiles and required data.
FAQ
Can team members see only their assigned browser profiles?
Members can receive access to selected profile groups. Creation, editing, exporting, proxy management, and other operations have separate permissions. After assigning access, have the member check which groups and profiles appear in their client. This verifies that their visible scope matches the accounts they are responsible for using.
Can two teammates open the same browser profile at once?
The same profile can be open on only one device at a time. Other members see occupancy information when they try to open it. For a normal handoff, the current user closes the profile and waits for sync before the next member opens it. Owners and admins can take over when necessary.
Are automation plugins visible to everyone on the team?
That depends on the plugin's Visibility setting: All team members, Only me, or Selected members. Owners and admins always have access to all plugins. A plugin a member cannot see is also absent from that member's MCP tools and Local API. Profile access and permission to run automation remain separate requirements.
Can an accidentally deleted team profile be restored?
If the current plan includes the recycle bin, deleted profiles first go there and can be restored. Without that feature, the same recovery option does not apply. Read the deletion prompt and check the plan before deleting profiles. Export any profile and data you need to retain before removing it.