Skip to main content
Organization Admin permissions are required to impersonate other users. Admins can’t impersonate other admins.
The Impersonate user feature is useful for testing that access grants work as expected.

Impersonating users

1
Navigate to Settings > Users and click on a user. Note: If testing an access grant, the user must have a user attribute value that excludes them from the grant.
2
At the bottom of the user’s details page, click Impersonate user.
3
Create a new workbook based on the connection you want to test. In this environment, you can verify what the user would and wouldn’t have access to and adjust their permissions accordingly.

Impersonating a pending invite

Only pending invites can be impersonated. Expired, declined, or revoked invitations are not eligible for impersonation.
You can impersonate a user who has been invited but hasn’t yet accepted their invite. This is useful for checking their permissions and validating dashboards before the user logs in for the first time. If you create content - such as folders or saved documents - while impersonating a pending invite, that content will be owned by the invited user. If the user later declines the invite or the invite expires without being accepted, the content will be owned by a non-member, similar to what happens when a user is revoked. When impersonating a pending invite, the impersonation banner displays a note indicating that the invite is still pending.

Impersonate vs View As

Omni provides two ways to test content as another user:
  • Impersonate user provides a full-session simulation where you experience Omni exactly as that user would. This includes all role-based restrictions, connection access controls, and permissions. Access it from Settings > Users by clicking on a user and selecting Impersonate user at the bottom of their details page.
  • View As is a quick preview mode available in dashboard and workbook File menus. It applies the selected user’s attributes to resolve dashboards, filters, and access grants, but does not simulate role-based restrictions or connection access. Use this for quick user attribute testing without leaving your current context.
Use Impersonate for comprehensive testing that includes role-based restrictions and connection access. Use View As for quick user attribute testing.