Share the profile, never the password.

Before you start

• AliasMode with a Cloud workspace and confirmed teammates
• One profile per shared account, with the password known only to its owner
• An agreement on who may open which profiles and when
• Two-factor authentication kept on the owner's device

Step-by-step

1. 1

   Give each account one profile

   The shared account lives in one AliasMode profile. Its password is entered once, by the owner, and persists as a session in the profile's user-data directory.

2. 2

   Invite the team to the workspace

   Add teammates to your Cloud workspace with member roles. Access is a workspace membership, not a credential copy.

3. 3

   Sync the profile

   After the owner's first session, Cloud sync uploads an encrypted version of the portable profile. Teammates download it to their own machines.

4. 4

   Hand off by closing

   One operator has the session open at a time. Closing the profile syncs the latest state; the next teammate opens it with all cookies intact — no password ever moved.

5. 5

   Keep 2FA on the owner

   Two-factor prompts go to the owner's phone. If a teammate triggers one, they ask the owner — which is exactly the audit trail you want.

6. 6

   Revoke, don't rotate (first)

   When someone leaves, revoke their device in the Cloud workspace the same day. Password rotation is a last resort; device revocation is the fast, complete cut.

7. 7

   Log the windows

   Keep a simple log of who had a profile open and when. It costs seconds and answers every 'who posted this' question.

The AliasMode workflow

1. 1

   Workspace roles

   Owner and member roles in Cloud decide who can hold profiles at all — keep members few and named.

2. 2

   Encrypted sync

   Portable profiles sync encrypted with version-based checks, so stale sessions never overwrite current ones.

3. 3

   Concurrent-open warnings

   AliasMode warns when a profile is open elsewhere, keeping one-writer sessions honest.

4. 4

   Device revocation

   Lost laptop, offboarded teammate: revoke the device in the workspace and access ends there.

Verify it worked

• A teammate opens the shared profile and lands in the logged-in session without asking for the password.
• Only the owner's device receives 2FA prompts.
• Revoking a removed teammate's device cuts their access immediately.
• The handoff log matches Cloud's version history for each profile.

Cautions

• Platforms still attribute all actions to the account; sharing access does not spread responsibility.
• Do not bypass the workspace by exporting profile folders manually — encrypted Cloud sync is the controlled path.
• Never paste credentials into shared documents or chat, even 'temporarily'; that copy is forever.