Clerk’s impersonation guide lists five free uses a month—and an Electron caveat

Clerk’s guide to building a custom user-impersonation flow lists an allowance of up to five free impersonations per month. The page is marked “Last updated on Oct 15, 2026,” but presents a how-to guide, not a feature launch. Developers who need a higher limit are directed to Clerk’s pricing page; the guide itself gives no price.

For Electron developers, there is a more immediate limitation: the Electron version of the guide says examples for that SDK are not yet available. It suggests adapting the available example, which uses Next.js. The page therefore offers a starting point, not an Electron-specific walkthrough.

Clerk describes impersonation as a way to sign in to an application as one of its users, allowing support staff or developers to reproduce that person’s problems. The sample builds a dashboard where an authorized user can select someone to impersonate and be redirected to the application’s homepage.

The example calls for a custom org:admin:impersonate permission, with authorization checks in the dashboard and the server action. That server action requests an actor token from Clerk’s Backend API; client-side code then uses the token to sign in as the selected user. Developers must create the permission first or replace the checks with authorization suited to their application.