Clerk docs spell out custom impersonation flow and its five-per-month free allowance

Clerk, the authentication provider, updated a documentation guide on October 15, 2026 that explains how developers can build their own user-impersonation flow. The page is Clerk's Electron variant of the guide. The documentation does not say the feature is new, so this is best read as a documentation update, not a product launch.

Clerk describes impersonation as a way to sign in to an application as one of its users, so developers can reproduce and fix problems that user is having, which Clerk calls useful for support and debugging.

The commercial detail is the allowance. According to Clerk, an application can perform up to five user impersonations per month for free, and the company points developers to its pricing page to raise that limit. This article did not review that pricing page, so the cost of going beyond five is unconfirmed.

Clerk says anyone who prefers prebuilt UI should use its Account Portal pages or prebuilt components instead.

The worked example builds an admin dashboard that lists the application's users and signs the administrator in as whichever one they choose. Access is limited to people holding a custom permission named org:admin:impersonate, which developers must create first or replace with their own authorization checks. Behind the button, a server action calls Clerk's Backend API to create an actor token, and the browser uses that token to sign in as the chosen user.

There is a caveat for Electron developers. The page itself says examples for that SDK are not yet available and suggests adapting the example from another SDK, which is written for Next.js. Whether the flow works the same way in Electron apps is therefore not shown on the page.

What remains uncertain: the page gives no changelog, so what changed on October 15 is unknown. Only one source was found. Other Clerk docs pages cover other SDKs but come from the same organization. A third-party pricing blog quoted a Clerk email from February 2026 about five free impersonations, but that was a quote of Clerk itself and concerned an earlier pricing change, so it is not treated as independent confirmation. All claims here rest on Clerk's own documentation.

Why it matters: impersonation gives an administrator the power to act as another person inside an application. The guide's emphasis on a dedicated permission check and a server-side token is a reminder to restrict who can use it.

Revised 16 October 2026: Guth re-read the original sources and rewrote this article. Correction: the earlier version said Clerk had added a user impersonation feature. The source is a Clerk documentation page last updated Oct 15, 2026; it does not say the feature is new, and its Electron version says Electron examples are not yet available. The earlier version remains available as revision 1.