> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omni.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Testing access grants and permissions with user impersonation

> Use Omni's impersonation feature to view the application as another user and verify that access grants and permissions work correctly.

> [!NOTE]
>
> **Organization Admin** permissions are required to impersonate other users. Admins can't impersonate other admins, and [email-only users](https://docs.omni.co/administration/users/email-only.md) can't be impersonated.

The **Impersonate user** feature is useful for testing that access grants work as expected.

## Impersonating users

**Step 1**

Navigate to **Settings > Users** and click on a user. **Note**: If testing an [access grant](https://docs.omni.co/modeling/develop/data-access-control.md), the user must have a [user attribute value](https://docs.omni.co/administration/users/attributes) that excludes them from the grant.

**Step 2**

At the bottom of the user's details page, click **Impersonate user**.

**Step 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 users in documents

You can impersonate a user without leaving a  document:

1. Click **File > View as**.
2. Select **Impersonate**.
3. Select a user to impersonate. **Note**: The user picker only lists users who can be impersonated.

This starts the same full impersonation session described above, then returns you to the current document as the selected user.

## Impersonating a pending invite

> [!NOTE]
>
> 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. You can access impersonation from the [user's settings page](#impersonating-users) or the [**View as** option in documents](#documents).

* **[View As](https://docs.omni.co/visualize-present/dashboards/view-as.md)** is a quick preview mode available in the same **File > View as** dialog. 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.