When a marketing agency takes on a new customer, it first aligns the business entity, platform assets, web page login session and member permissions, and then arranges the antidetect browser environment. This article uses a customer access example to illustrate how to reduce account mix-ups, duplicate configurations, and missing permissions.
After a new customer hands over their account to the agency team, the easiest thing to do first is find a computer and log in. Once the advertising, content, and customer service teams start working, the team discovers that the same customer has several business entities, several accounts use the same browser data, and temporary collaborators could see environments that did not belong to them.
The actual use of the antidetect browser in this scenario is to organize different customers’ work sessions into identifiable, assignable browser environments that can be used continuously. Building more environments does not mean that customer management is clear; the key lies in whether assets and users are matched during onboarding.
What Is Antidetect Browser? FULL Explainer + 4 Real Life Cases on YouTube illustrates this type of need using a marketing agency, international clients, and a remote team. To apply these scenarios to the actual work of onboarding new clients, you can first solve the following problems.
List customer assets first, and then decide how many environments to build
A customer does not necessarily have only one web login session, and a member should not automatically have a general-purpose environment that can log in to every client’s accounts.
Suppose an agency takes over two customers A and B at the same time: customer A has a brand content account and an advertising work account, and customer B has two brands operated separately. At this time, it is more useful to separate them by "Business Entity and Work Session" first, rather than first deciding how many windows each person should open.
The onboarding inventory can retain only these fields:
| Items that need to be checked | What should be written clearly | What this helps determine |
|---|---|---|
| Customers and business entities | Customer number, brand or store ownership | Which customer group the environment belongs to |
| Platform assets | Platform page, store, advertising assets or dashboard/backend name | What will be operated during this onboarding |
| Account and login portal | Which authorized account to use and where to log in | Which sessions need to be maintained separately |
| Work roles and owners | Main operator, reviewer, collaborator | Who can access the corresponding environment |
| Network and work locations | Existing proxies, usual work locations, and who owns changes | How to keep network configuration traceable |
What is recorded here is the working relationship that the customer has authorized. When the platform has formal member invitation, employee seats or asset authorization functions, this relationship should be fully configured first; the browser environment is responsible for hosting work sessions and cannot replace member permissions within the platform.
Environments are divided by sessions and groups are organized by customers
Two questions need to be answered separately: which login states need to be kept independently, and how can the team quickly find them.
The former determines the number of environments, and the latter determines the grouping method. Web page login sessions that need to be maintained separately can be put into their own browser environments; these environments for the same customer can then be grouped into customer groups. Don't remix sessions that need to be processed independently into one environment just to keep the list tidy.
Environment names can be in a simple fixed order, for example:
Customer number|Brand or business line|Platform|Work purpose
In this way, the operator can confirm "which job is for which customer" before opening the environment. There’s no need to put a password, verification code, or full recovery information in the name, or a long list of abbreviations that only the creator can understand.
If a client only needs to deal with one dashboard and doesn't have multiple people collaborating on it, start with the minimum number of environments needed to do the job. When independent business lines or work sessions appear later, they can be expanded according to actual needs instead of establishing a large number of empty environments in batches at the beginning.
Fingerprint parameters, proxies and login status are maintained as a set of configurations
An environment doesn't just have a name. The team also needs to know the proxy it is bound to, the login status it saves, and who maintains the related configuration.
The browser environment can separately maintain cookies, website storage, and fingerprint-related settings; the proxy is another configuration of the network exit. Just changing an environment name will not change the network exit; just changing a proxy cannot replace organizing the browser session.
When onboarding new customers, a more practical approach is to record the current configuration and purpose of use, and then establish change rules: who can change proxies, under what circumstances the environment needs to be adjusted, and how to confirm that the correct client dashboard is still entered after adjustment. Do not regard frequent parameter changes as routine maintenance actions.
If verification or restriction occurs after logging in, it should be handled according to the process provided by the platform, and the time of occurrence and environmental changes at that time should be recorded. You cannot promise that verification will disappear, that accounts will not be restricted, or that the platform will not recognize the business relationship between accounts based on browser configuration alone.
What members get is the scope of work, not the entire customer base.
After onboarding the environments, the next step is to assign scope of work. Content members may only need to access the brand content dashboard; advertising team members are responsible for advertising assets; reviewers need to confirm the results, but may not necessarily be responsible for all daily operations.
In PurpleMark, checked environments can be classified into corresponding groups, and access scope can be organized by combining members, roles, and authorization groups. Environment sharing, transfer and operation logs are used for subsequent collaboration and recording. Determining "who is responsible for which work" before onboarding is easier to manage than opening the environment to everyone after it is built.
You can first download the PurpleMark client, log in and create an environment group for a real customer, and use a small number of environments to check the naming, member access range and startup entry. After confirming that each member can access their assigned work environment, apply this set of configuration rules to other customers.
After the first login, complete an onboarding check
The fact that the account can be opened only proves that the login step is completed. Before formally arranging work, the actual users should also complete their tasks once.
For example, let content members enter the backend of the target brand and confirm that they see the correct brand and page; let advertising team members check customer assets and work accounts; let reviewers confirm that the corresponding environment and necessary records can be found. Use normal work actions permitted by the customer for testing, and avoid batch registration or abnormal operations for the purpose of "testing isolation".
Acceptance can record four results:
- Assets are correct: The account, brand, store or advertising assets are consistent with the onboarding inventory.
- Access scope is correct: Members can find the responsible environment, and other customer scopes are managed according to established permissions.
- Someone is responsible for the configuration: Proxy and environment configurations have maintainers, and records of changes can be found.
- Exception handling path: When encountering account verification, insufficient permissions or configuration changes, you know who to contact and which record to check.
Once these points are confirmed, the client setup is ready to hand over to the team for ongoing work.
FAQ
Does each customer have to build only one browser environment?
Not necessarily. A customer represents business ownership, while a session is the unit of work. A client may require several separate sessions, or just one; check the working relationship first and then decide on the quantity.
Are different user profiles for normal browsers enough?
If the main need is just to save login status separately, a normal browser profile may do part of the job. As more environments, proxy configurations, and team access scopes need to be managed centrally, then evaluate whether antidetect browsers can reduce the workload of distributed maintenance.
After the environment is built, do I still need to configure platform member permissions?
Yes. Check them separately. The browser environment determines which work session to enter from, and the platform permissions determine what operations can be performed after entry. During onboarding checks, both layers must be confirmed by actual users.


