Team Profile Sharing and Permissions

MaskPilot team collaboration is built around members, profiles, and explicit permissions. The owner can invite members, assign visible profiles, and separately control whether a member may create or modify profiles, manage proxies, share profiles, or use AI capabilities.

Assign profiles before granting actions

“Which profiles are visible” and “which actions are allowed” are separate decisions. Assign only the profiles a new member needs, then enable feature permissions for that role. This distinction makes missing-profile and denied-action problems easier to diagnose. Use separate checklists when a member cannot see a profile and when a member can see a profile but cannot edit it.

Understand profile sharing

One-time sharing creates a new profile for the recipient with the browser version, entry-proxy configuration, and fingerprint settings. It does not copy browser data or extension assignments, transfer ownership, delete the sender’s profile, or keep both profiles linked. Each side maintains its own profile afterward.

Keep access traceable

Grant only the permissions required for the work and remove them when responsibilities change. Team activity records help review member and profile actions, but good access design should begin with a narrow scope rather than relying on an investigation later. For an unexpected change, use the profile activity record checklist to filter by profile and action, identify the operator, and understand the record’s limits. When a sensitive member action does not finish immediately, use the pending team action checklist to verify the requester, target profile, and review result.