The shift towards passwordless authentication is creating new considerations for agencies that manage multiple client accounts. In 2023, Google announced that passkeys had been used to authenticate users more than one billion times across its services. By 2025, platforms including X, LinkedIn and Meta had expanded their support for passkey authentication.
For social media managers and agency operators juggling dozens of client accounts, this raises a practical question: how do you manage passkeys across multiple accounts without mixing up credentials or losing access?
There are many answers to that question, but this guide walks through how Incogniton anti-detect browser’s approach. We will talk about how passkeys work in Incogniton, why per-profile management matters for agencies, and the exact setup steps to keep every client account secure.
TL;DR
- Incogniton helps agencies manage passkeys across multiple client accounts by storing each credential separately within its own browser profile.
- Each profile has an isolated passkey store, preventing credentials from different client accounts from getting mixed up.
- Teams can share profiles through cloud synchronisation, allowing authorised members to access saved passkeys without sharing personal password-manager credentials.
What Are Passkeys and How Do They Work?
A passkey is a digital credential that allows someone to sign in without entering a password. It uses a pair of cryptographic keys: a private key stored on the user's device or authenticator and a public key registered with the website.
When someone attempts to log in, the website sends a challenge that the private key must sign. The user approves the request using a fingerprint, facial recognition or device PIN. The website verifies the response without receiving the private key.
This makes passkeys more resistant to phishing than conventional passwords. A passkey is also tied to the website for which it was created, so a fake login page cannot simply collect and reuse it.
Why Managing Passkeys Across Multiple Accounts Can Be Difficult
Most conventional passkey setups rely on a shared storage location, such as Windows Hello, Apple iCloud Keychain or Google Password Manager. This works well for individuals but can become complicated when an agency manages several client accounts on the same platform.
For example, if you manage multiple TikTok accounts in Chrome, passkeys may be stored through the same system-level credential manager. Depending on your browser and operating system configuration, this can make it harder to distinguish between credentials associated with different accounts.
There is also the issue of device identification. Some platforms consider device and browser characteristics when assessing login activity. Managing several accounts within the same browsing environment can therefore introduce inconsistencies that complicate account management. Understanding the difference between a browser fingerprint and a device fingerprint helps explain why maintaining separate browsing environments matters.
Sharing access presents another challenge. Passkeys stored in an employee's personal Google or Apple account are not automatically available to other team members. Sharing an entire password manager is rarely a practical solution, particularly when employees handle different clients.
How Incogniton Anti-detect Browser Manages Passkeys Differently
One big difference between conventional browsers and an antidetect browser passkey setup is how the credentials are stored.
As we mentioned earlier, web browsers like Chrome or Safari use a shared storage location which is convenient for personal use but dangerous for client work. In anti-detect browsers like Incogniton, however, the isolated environment of the browser profiles means this is not the case. Each profile has its own Chromium-based engine, its own local storage, and its own passkey database.
A passkey created inside Profile A never appears in Profile B. The cryptographic material, user verification settings, and session state remain contained. The associated authentication data and session information stay within their respective profiles.
Managing passkeys per profile like offers three tangible benefits:
- No Cross-Account Authentication Errors: When passkeys live in a shared store, the browser may autofill the wrong credential. With per-profile storage, the passkey offered during login is always the one tied to that profile. You never see Client B’s passkey when you’re working in Client A’s environment.
- Cleaner Security Audits: If a client asks which devices have access to their account, you can point to a specific Incogniton profile. The passkey is bound to that profile’s fingerprint and proxy. There’s no ambiguity about where the credential lives.
- Safer Team Handoffs: When a team member leaves or a client is offboarded, you can delete the corresponding profile. The passkey goes with it. No lingering credentials remain on shared machines or cloud sync accounts.
What Happens When You Share a Profile?
Incogniton supports team access with role-based permissions and so the question is how does this work with the passkey management setup.
Another feature of Incogniton is the cloud sync. When you enable it, it allows profile data to synchronise across computers and with teammates who have access to a shared profile. For team collaboration features, this feature is enabled. This means instead of registering a new passkey on every employee's computer or sharing personal password-manager credentials, the agency can share the relevant browser profile and the passkey travels with the profile. The authorised team members are to use it when they open that environment.
For example, a team member can open Profile A, access the relevant client account and authenticate using its saved passkey without having to register a new credential on their computer.
When an employee leaves, an administrator can revoke their access through the Incogniton dashboard. The profile and its stored passkeys remain available to other authorised team members, avoiding unnecessary password resets or disruption to the client's account.
There is, however, an important security consideration: anyone who can open a profile may be able to use the passkeys stored inside it. Profile access should therefore be treated as access to the client accounts associated with that environment..
How to Set Up a Passkey in Incogniton Browser Profiles
Setting up passkeys in Incogniton follows the same general workflow.The important thing is to configure the profile before enrolling the passkey so that the credential is stored in the intended environment.
Step 1: Create a Dedicated Profile
Open Incogniton and click New Profile. Name it after the client or account it will serve. Avoid generic names like “TikTok 2” that can cause confusion later.
Step 2: Assign a Proxy and Fingerprint
Before enrolling any passkey, configure the profile’s proxy and fingerprint settings. Use a dedicated proxy that matches the client’s target region. Set the timezone, language, and screen resolution to align with the account’s expected environment. This ensures the passkey is created under the correct identity context.
Step 3: Launch the Profile and Enroll the Passkey
Open the profile and navigate to the platform’s security settings. Follow the platform’s passkey enrollment flow. When prompted, use the profile’s built-in passkey manager to store the credential. The passkey is now bound to that profile.
Step 4: Test the Login
Close the profile, relaunch it, and attempt to sign in using the passkey. Confirm that no other passkey is offered. If the correct passkey appears, the setup is complete.
Step 5: Document the Profile
Record which profile holds which passkey in your internal documentation. Include the profile name, platform, account handle, and date of enrollment. This makes audits and handoffs straightforward.
Best Practices for Managing Client Passkeys
Even with a solid setup, agencies make a few recurring errors with passkeys multiple accounts. Consider these practices when introducing passkeys into your workflow.
Assign One Profile to Each Client
Avoid storing credentials for unrelated clients in the same profile. Create a consistent naming convention, such as Client Name – Social Media, so employees can identify the correct environment.
This also makes it easier to manage access when a client leaves or an employee changes responsibilities.
Maintain Alternative Recovery Methods
Do not rely entirely on passkeys. Keep an alternative authentication method, such as an authenticator app or recovery codes, for every important client account.
If a profile is accidentally deleted or becomes inaccessible, these alternatives can help restore access. Remember that deleting an Incogniton profile also deletes the passkeys stored inside it.
Control Who Can Access Profiles
Use Incogniton's team management and profile-sharing permissions to restrict access to employees who need it.
For example, a social media manager responsible for three clients should not automatically have access to every profile in the agency. Review permissions when employees join, change roles or leave.
Protect Your Incogniton Account
Your Incogniton account controls access to your browser profiles and the passkeys they contain. Enable two-factor authentication (2FA) on your Incogniton account and use a strong, unique password.
Also, avoid opening client profiles on public or untrusted computers. Anyone who gains access to a shared profile may be able to use its saved authentication credentials.
Conclusion
Managing passkeys across multiple accounts no longer requires risky workarounds or shared keychains. Incogniton’s per-profile passkey storage gives agencies a clean, isolated way to authenticate into every client account without cross-contamination. Each passkey browser profile acts as its own secure device, with its own fingerprint, proxy, and credential store.
For social media managers, operations leads, and freelancers, this is the practical path to passwordless security at scale. Set up dedicated profiles, enroll passkeys inside them, and document everything. The result is faster logins, fewer security incidents, and a workflow that scales as your client roster grows.
To see how Incogniton passkeys work in practice, explore the browser profile setup guide and learn more about keeping profiles unique.
