Login as a teammate
Owners can use a teammate's actual workspace permissions for a bounded session without accessing personal settings or unrelated workspaces.
Login as lets a workspace Owner enter the workspace as an Admin, Manager, or Member teammate. It is available on every plan and does not require the teammate's password.
This is a real session, not a read-only preview. Ordinary actions use the teammate's actual permissions and can change records or trigger their normal notifications and deliveries. Use it deliberately, especially when reviewing an Admin's access.
Start and stop
- Open the teammate's full member profile from your team. The route is
/people/[userId]. - As the workspace Owner, choose Login as in the profile header, before Change role and Manage access.
- Check the persistent impersonation banner before working. It is visible on desktop and mobile.
- Choose Stop impersonating to return to your Owner session and the teammate's profile.
The button is not available for your own profile, another Owner, or while already impersonating. Admins, Managers, and Members cannot start delegation. The session affects this browser's tabs; do not assume another tab is still acting as the Owner.
Sign out signs out completely, rather than returning to a hidden Owner login. Delegation lasts at most 30 minutes, and never beyond the Owner's original session expiry. Expiry, lost required membership/ownership, or a security revocation ends the session and requires signing in again; a pending action does not silently gain Owner permissions.
What is and isn't available
Only the shared workspace is available, with the target's live role and project access. Login as does not reveal their other workspaces or upgrade their plan or permissions. For example, a Member remains money-blind, and a Manager still cannot open private Payouts.
End delegation before using personal account settings, password/email/2FA/passkey controls, API token or extension-device management, notification preferences, Telegram linking, workspace creation/switching/leaving, or extension authorization.
Ordinary record changes keep their existing histories. Starting Login as does not create a separate login/admin audit event; it is not an operator-attributed audit trail. Customer analytics and authenticated support-chat presence are suppressed during delegation.
Troubleshooting
- No Login as button: confirm you are the Owner, viewing another non-Owner teammate's full profile, and not already impersonating.
- An account action is blocked: choose Stop impersonating first.
- The session ended: sign in again and check the current role/membership before restarting.
See Roles explained and Project access for what the delegated role can do.