Clerk Changelog

When customizing session tokens, you can now preview the resulting claims before saving your changes.

Select a user to generate claims based on the current template. This lets you verify that custom claims, template expressions, and organization data produce exactly the claims you expect.

Previously, saving a template then inspecting a real session token was required to check the template is correct. Preview lets you ensure expected behavior before impacting real users.

You can now prevent end users from adding new or modifying existing email addresses, phone numbers, or usernames after they have signed up through the new Restrict changes toggle in the Clerk Dashboard. Navigate to the User & authentication⁠ page to enable.

Enabling this feature gives you the ability to have maximal control over the exact identifiers your end users can use to sign in to your application. If you'd like to control which identifiers are allowed at sign-up rather than locking them afterwards, see restrictions for allowlists, blocklists, and disposable email blocking.

With this setting enabled, your end users will still be able to view their identifiers in their User Profile, but will not be able to add, remove, or modify the respective identifier. For email addresses, this restriction extends to social connections: End users are prohibited from connecting an OAuth account that would otherwise add a new email address to their account.

Of course, you still have the ability to modify their end users' identifiers at any time on the Users page of the Clerk Dashboard⁠ or using our Backend API⁠.

If you would like to have support for restricting end users from changing other attributes than email address, phone number, or username, please reach out to us to share this feedback.

Starting today, membership limits on organizations can be granted directly by subscribing to a Clerk Billing plan, allowing organizations to purchase a higher membership limit in a self-serve fashion.

This makes it possible to target plans to organizations of specific size. For example, you may let organizations use your most affordable plan for up to ten seats, but require them to upgrade to a more expensive plan to get unlimited seats.

Seat limits are enforced automatically through the integration of Clerk's Billing and B2B Authentication products. When an organization hits its seat limit, Clerk will prevent adding additional members and guide users toward upgrading.

More seat-based features to come

This release is our first step towards seat-based billing for Clerk Billing. We know that many use cases require organizations to be able to purchase a specific number of seats specified at checkout at a per-seat cost; we hope to have more to say on that functionality in the near future. We're excited to ship this first step into seat-based billing and to expand on it.

How to create a seat-limited plan

• Navigate to the New Organization plan⁠ page in your instance's settings.
• Toggle on the Seat-based section.
• If you'd like the plan to convey an unlimited number of seats, leave Unlimited members selected. (You need to have the B2B Authentication add-on to select this option.)
• If you'd like to set a limit, select Custom limit and enter the limit.

This new section brings the most relevant waitlist information into one place, so you can understand sign-up access without jumping between pages.

This makes it easier to see how many users are waiting for access, how many have already been invited, and which recent entries may need follow-up.

Features

• Waitlist counts: Track how many users are on the waitlist, how many have been invited, and how many have been accepted.
• Recent entries: Review recent waitlist activity directly from the Overview page, including a new infinite scroll table for large waitlists.
• Faster follow-up: Jump from the overview to the full waitlist view when you need to take action.

Open the Overview page for your production instance in waitlist mode in the Clerk Dashboard⁠ to see the new experience.

You can now add authentication and user management to your app through Stripe Projects⁠. Available in developer preview, this CLI-based workflow lets teams and AI agents provision Clerk directly from the terminal.

Using the Stripe CLI, you can:

• Connect an existing Clerk account or have one created for you
• Provision a new Clerk application with both development and production credentials
• Manage authentication keys, rotate secrets, and access your Clerk dashboard — all from Stripe

To get started, install the Stripe Projects plugin for Stripe's CLI and initialize your project:

Select Clerk to add authentication and start building, or visit the documentation to learn more.

The organization activity report shows daily member engagement levels for each org, helping you understand how teams are using your product.

• Visualize engagement - Each day in the report is color-coded by the percentage of total organization members who were active, making it easy to spot trends and patterns.
• Navigate by year - Use the year selector to browse activity across different years.
• Hover for details - Tooltips show the percentage of org members who were active on each day.

Note: Activity data is available starting from January 2026.

To view the activity report, open any organization's profile page from the Organizations⁠ list in your Clerk Dashboard.

Keep an eye out for continued improvements to the organization profile page.