User Impersonation
Learn how to impersonate a user and perform actions on their behalf.
User Impersonation allows account administrators to temporarily act as another user in the account, including other admins without needing their password. This feature is especially useful for troubleshooting, and verifying if a user has the intended set of permissions.
By impersonating a user, Account admins can see exactly what that user sees and perform actions on their behalf.
Demo video
Prerequisite
A user must have the Account Admin role to impersonate other users.
How to impersonate a user
Navigate to Account Settings, Access Control and select Users.
For the user you want to impersonate, click the vertical ellipsis icon (:) on the right, and select Impersonate User.
For each impersonation session, you must provide a valid reason. Once entered, click Start Impersonation to begin the session.
The impersonation session lasts 30 minutes. A banner at the top of the screen shows the remaining time for the session.
To end the impersonation session midway, click the End Session button on the top banner.
When the session ends, a prompt appears giving you the option to either Restart Session or Quit.
View impersonated user info
You can view the impersonated user info in the pipeline execution history. This allows you to identify the impersonator and the impersonated user.
Impersonation session audit events
The Start impersonation audit event is triggered at the beginning of an impersonation session, while the End impersonation audit event occurs when the session concludes or times out.
All audit events fired during the impersonation session are tagged with the impersonator and impersonated user details. These can be viewed in the Audit Trail page.
The Action column shows the activity, while the User column indicates who was impersonated and by whom.
IMPORTANT NOTE
The Impersonate User option is available only at the Account scope.
Only users that have logged in at least once can be impersonated.
The following are not supported during an impersonation session:
Self-impersonation
Creating, editing, or deleting API Keys or Access Tokens
Account-related actions such as:
Viewing list of accounts for an impersonated user
Switching accounts
Changing the default account
Signing out
Resetting passwords
Managing Two-Factor Authentication (2FA)
Changing state of public access or managing IP allowlist
Last updated
Was this helpful?