Impersonation lets you see DataMind OS as another user does, with the same roles and data access, so you can check what they see. Use it to troubleshoot a problem without asking for their password.
You need the User Impersonation permission. In the permission editor, it is a Standard set that contains View Users and Impersonate User. Users Administrator does not include it, so you must grant it separately. The built-in Admin role always holds it. Impersonation has no settings of its own. For every Standard permission, see the Permission reference.
The picker shows 20 users at a time. Click Load more to see the rest. If nobody can be chosen, it reads Nobody to act as; a search that finds nothing reads No user matches that search.
The row action and the panel action appear only for a person you may view as, so they are not offered for inactive users, for members of the built-in Admin role, or for yourself.
You can view as an active user who has at least one active role and is not you. Anyone who holds Impersonate User is excluded, including every member of the built-in Admin role, because the Admin role holds that permission itself.
If a view is refused, the confirmation shows the reason:
If the switch fails for another reason, the confirmation shows "Could not act as this user. Please try again."
A pill at the bottom of the screen reads Viewing as, followed by the person's name and email, and has an Exit button. It stays on every page.
Changes you make while you view as someone are real. They are recorded against both of you.
Click Exit in the pill. DataMind OS returns you to your own account and reloads.
If the person is deactivated or loses access while you view as them, the pill reads the person's name followed by "can no longer be viewed". Click Exit to leave.
Open Observability > Logs > Audit to see recorded requests. For requests made while you were impersonating, the User column shows the person you viewed as, and the Acting as column shows who was signed in. You need access to Observability to open the logs. See Audit, sign-in and notification logs.
For messages you may see on this page, see Administration troubleshooting.
Yes. They are real, and they are recorded against both of you. Some actions are blocked, as listed above.
No. Their private chats stay hidden while you view as them, including the person's own private chats.
Members of the built-in Admin role, and anyone who holds Impersonate User, cannot be viewed as. The Admin role holds that permission itself, so its members are always excluded.
Everyone who could be chosen is excluded: inactive users, users with no active role, people who hold Impersonate User, and you. If nobody is left, the picker shows that message.
Click Exit in the pill at the bottom of the screen. DataMind OS returns you to your own account and reloads.
The person was deactivated, or lost access, while you were viewing as them, so the session shows you nothing. Click Exit to leave.
No. You do not need their password or their two-factor code. Confirm the session, and it starts.
Only people who hold Impersonate User, for example through the User Impersonation set.
A Mind on Execute as User cannot run SQL while you view as someone, and neither can Warehouse Builder or Lake Builder Minds. Minds on Owner Role keep running SQL. Exit the view to use these Minds for SQL again.
Private chats, alert changes, content logging, Model AI changes and reverts, custom visual code, Model Builder actions, and SQL on Execute as User and builder Minds. The sections above list each one with its message.