Impersonation and support
Introduction
Impersonation is an advanced feature that lets an administrator temporarily sign in as a user to assist them. It is designed with strict safeguards to prevent abuse.
What is impersonation?
Impersonation lets an admin see the platform exactly as the user does and perform actions on their behalf to:
- Diagnose an issue reported by the user
- Fix incorrect configuration
- Walk a user through a process step by step
- Resolve a technical blocker
Impersonation security
Each impersonation session is:
- Protected by a confirmation code: a unique code is generated for each request
- Logged: all actions performed are recorded
- Temporary: the session can be ended at any time
How to impersonate
Step 1 — Identify the user
- Find the user in the list (Investors or Companies).
- Note their ID or email.
Step 2 — Request an impersonation code
- From the admin menu or the user profile, open "Impersonation".
- Click "Request code".
- Enter the identifier of the user to impersonate.
- Submit the request.
The system generates a unique, single-use impersonation code.
Step 3 — Verify the code
- You receive the code (by email or in the interface).
- Click "Verify code" or "Use code".
- Enter the code you received.
- Confirm.
Step 4 — Impersonation mode active
Once the code is validated:
- You are signed in as the user.
- A warning bar at the top of the page shows impersonation mode.
- The bar shows the impersonated user’s name and an "Exit impersonation" button.
Exit impersonation mode
To return to your admin account:
- Click "Exit impersonation" in the top warning bar.
- You return immediately to your normal admin session.
Important: Do not close the window without exiting impersonation. Always use the dedicated button to return to your account.
What is logged during impersonation
During an impersonation session, the following are recorded in the logs:
- The identity of the admin who impersonates
- The identity of the impersonated user
- Start and end date and time
- Actions performed during the session
These logs enable full transparency and help prevent abuse.
Usage rules
- Obtain the user’s consent before impersonating (except documented exceptional cases).
- Only perform actions needed to resolve the issue.
- Exit immediately once the problem is solved.
- Document what you did and why in support notes.
- Do not change sensitive information (password, bank details) without explicit consent.
Common use cases
| Situation | Recommended action |
|---|---|
| User cannot find a feature | Impersonate and show where it is |
| Payment is stuck | Check transaction status from their account |
| Document will not upload | Test upload from their account to reproduce the bug |
| A form is blocking | Identify the faulty field by testing live |
Support chat
Alongside impersonation, chat is often enough to resolve most issues without impersonating.
For more on chat, see Module 1 — Chat system.
Previous: Module 9 — Platform settings Next: Chapter 6 — Shared features