AI assistants: this page is available as Markdown at https://documentation.cluedin.net/administer/users-and-roles/impersonate-user.md. The index of the whole documentation, with instructions for AI assistants, is at https://documentation.cluedin.net/llms.txt.

Impersonate a user

how-to Steps to accomplish one task

On this page

1. Prerequisites
2. Start impersonating a user
3. Stop impersonating
4. What this changes
5. Audit log reference
6. If something goes wrong

Impersonation lets an OrganizationAdmin temporarily view CluedIn exactly as another user in the organization sees it - to confirm that user’s permission and RACI setup, or to reproduce an access issue they reported - without knowing their password, and without logging out of your own account.

This article is intended for users with the OrganizationAdmin role.

Section	Claim	Access level
Admin	Users	OrganizationAdmin role required

Prerequisites

• You must have the OrganizationAdmin role. Impersonation is not available to any other role, regardless of claim access level. For more information, see Roles.
• The user you want to impersonate must belong to your organization. You cannot impersonate yourself.

Start impersonating a user

1. On the navigation pane, go to Administration > User Management.

2. On the All users page, find the user you want to impersonate.

3. In the Impersonate column, select Impersonate.

   

CluedIn reloads and signs you in as that user. A banner stays visible at the top of every page for as long as impersonation is active, showing which user you are viewing CluedIn as.

While impersonating, you see exactly the modules, features, and data the impersonated user can see - including anything restricted by their RACI permissions. Admin-only screens, such as User Management itself, show You do not have access unless the impersonated user also has that access.

Stop impersonating

1. In the impersonation banner at the top of the page, select Stop impersonating.

CluedIn reloads and returns you to your own account. You do not need to sign in again.

An impersonation session also ends on its own after 1 hour. If it ends while you are still reviewing something, start it again or select Stop impersonating and sign back in if prompted.

What this changes

Impersonation does not change the impersonated user’s account - their password, roles, and data stay exactly as they were. It only changes what you, the admin, see while the session is active. Any changes you make while impersonating (for example, editing a record) still happen, and are attributed to the impersonated user, exactly as if they had made the change themselves.

Audit log reference

Starting and stopping impersonation is recorded on the Audit Log tab, including the timestamp, the admin who started or stopped it, and the impersonated user.

If something goes wrong

• If you don’t see the Impersonate column or link next to a user, you don’t have the OrganizationAdmin role.
• You cannot impersonate yourself - no Impersonate link appears on your own row.
• You cannot impersonate a user outside your organization.