From client setup to the next shift
Explore the responsibilities and actions at each step.
Create the client environments
Group profiles by client, choose Chrome / Chromium or Firefox, and reuse common proxy and fingerprint settings through templates.
Invite the team
Add members and assign roles that match their responsibilities. Keep platform account permissions aligned with the work assigned.
Work in the right context
Use profile names, tags and notes to identify the client and task before opening a session. Choose window synchronization or automation for repeated operations.
Hand over with context
Close the environment to complete Cookie archiving, update the task note and review relevant operations in the audit log.
Manage access as the team changes
Mango’s first release includes team management, invitations, roles and audit logs. Invite a new teammate, change a role when responsibilities change and remove members when access is no longer needed.
Folders and tags organize the work; roles control team operations. Keep publication approval in your established review process, alongside the browser workspace.
Make recurring browser work easier
Use window synchronization for repeated interactive operations across browser windows. For tasks maintained in code, use Local API to manage environments and launch browsers. Through MCP, an AI tool can navigate a selected profile, read page content, interact and capture a screenshot.
Templates and bulk actions help prepare the environments before the task begins. Keep client-specific content tied to its own profile when a task needs individual review.
Give the next operator useful context
| Context | Where to keep it | Purpose |
|---|---|---|
| Client and task | Profile name, folder and tags | Find the correct environment |
| Current work | Profile note and team task system | Explain the next step |
| Access | Team member and role settings | Keep responsibilities current |
| Changes | Audit log and task record | Review actions and follow-up work |