# Impersonation

## Introduction

Impersonation allows administrators to view Duvo from a team member's perspective. This is useful for debugging issues, reviewing configurations, and understanding what a specific user sees in their workspace.

***

## What is Impersonation?

When you impersonate a user, you can:

* See their assignments and configurations
* View their job history and results
* Understand their workspace setup
* Diagnose issues from their point of view

This helps you resolve issues without requiring team members to share screenshots or describe their setup in detail.

***

## When to Use Impersonation

### Troubleshooting Issues

When a team member reports a problem:

1. Impersonate to see exactly what they see
2. Reproduce the issue in their context
3. Identify the root cause
4. Provide specific guidance

### Reviewing Setup

When checking a team member's workspace:

1. Review their initial setup
2. Check their assignments
3. Identify configuration issues
4. Recommend improvements

### Configuration Review

When auditing or optimizing:

1. Review how assignments are configured
2. Check connections
3. Verify settings are appropriate
4. Recommend improvements

***

## How Impersonation Works

### Starting an Impersonation Session

1. Access the impersonation feature from admin tools
2. Select the user you want to review
3. A temporary session is created
4. You now see Duvo from their perspective

### During Impersonation

While impersonating:

* You see the user's assignments and runs
* You can view their configurations
* Actions may be limited to viewing only
* The session is logged for security

### Ending Impersonation

When finished:

* End the impersonation session
* Return to your normal view
* Document any findings
* Follow up with the team member as needed

***

## Best Practices

### Before Impersonating

* Have a clear reason for the impersonation
* Inform the team member if appropriate
* Know what you're looking for
* Document the reason

### During Impersonation

* Focus on the specific issue
* Don't browse unnecessarily
* Note relevant findings
* Respect user privacy

### After Impersonating

* Document what you found
* Communicate findings to the team member
* Implement or recommend fixes

***

## Security and Privacy

### Audit Trail

All impersonation sessions are logged:

* Who impersonated whom
* When the session occurred
* Duration of the session
* This ensures accountability

### Appropriate Use

Impersonation should only be used for:

* Responding to reported issues
* Diagnosing problems
* Authorized audits and reviews

### User Notification

* Users may be notified of impersonation sessions
* All sessions are logged regardless of notification settings

***

## Limitations

### What You Can't Do

During impersonation, you typically cannot:

* Make permanent changes to user accounts
* Access sensitive credentials
* Run assignments on behalf of users
* Modify billing or subscription settings

### View-Only Access

Impersonation is primarily for viewing:

* See what users see
* Diagnose issues
* Understand configurations
* But not make changes for them

***

## Things to Know

* Impersonation requires administrator privileges
* All sessions are logged for security
* Use impersonation responsibly and purposefully
* Document findings to improve future troubleshooting