Clerk Changelog

Instant Component previews

Sign-up, sign-in, and user profile components can now be previewed instantly after an application is created in Clerk - no code required! Just click the preview buttons on thie sidebar.

Thanks to the contributors: Marcel Cruz

In-house docs

Piece-by-piece, we're moving our documentation in-house! Our previous vendor was great for written documentation, but we constantly found ourselves wanting to add dynamic and interactive elements to our documentation.

With our new solution, built on Sanity and Next.js, we can more easily develop custom elements in our documentation. Stay tuned as our onboarding gets even easier in the months ahead.

The new documentation is available on clerk.dev/docs.

Thanks to the contributors: Charles Wefso, Ian McPhail

Email deliverability improvements

We noticed a small subset of customers we're having a few email deliverability issues. In particular, the customers who launched a brand new application on Clerk and have never sent emails from their domain before. These developers had zero "domain reputation" and gmail was delaying the delivery of magic links and sms codes.

This week, we made three small adjustments that seem to have resolved the issue:

1. Improved the formatting of the plaintext "part" of our emails
2. Removed unnecessary query string variables and & with just &
3. Removed the application name from the email subject

We will continue to monitor deliverability and make adjustments as needed.

Thanks to the contributors: Agis Anastasopoulos, Haris Chaniotakis

Community spotlight: Supabase Launch Week!

Congratulations to Supabase on their tremendous launch week!

Supabase is an incredible product and we share many customers through our Supabase integration.

We're proud to have launched our integration in their new Partner Gallery this week, but also just really excited to try their new functions.

Bring-your-own IdP with Sign in Tokens

Clerk now be configured to work with external identity providers (IdPs)!

Sign in Tokens are a low-level abstraction that offers developers complete flexibility when signing in users. It allows you to handle user authentication on your own and then delegate session management to Clerk.

The primary use case for tokens is keeping authentication with a Customer Identity vendor like Auth0, but taking advantage of Clerk's SDKs for easier integration with the Jamstack ecosystem of frameworks, databases, and other tools.

Sign in Tokens can be generated securely with Clerk's backend API.

Thanks to the contributors: Alex Ntousias, Giannis Katsanos

Allowlist for sign ups

We've added a Sign-up restrictions tab to the dashboard where you can restrict sign ups to your application by email domain, email address, or phone number.

The allowlist restrictions can also be enabled by API to produce a programmatic invite-only flow.

Thanks to the contributors: Giannis Katsanos, Nikos Petridis

Sign in with Apple

We've added Sign in with Apple to our growing list of social login providers!

Thanks to the contributors: Agis Anastasopoulos, Haris Chaniotakis

Organization roles in custom JWTs

A new shortcode has been added to JWT templates for developers participating in our Organization Management early access.

The token is called {{user.organizations}} and it returns a dictionary of the user's organization IDs mapped to their role in that organization. This is particularly helpful when performing authorization checks within database vendors like Supabase, Hasura, Firebase, or Fauna.

Thanks to the contributors: Haris Chaniotakis

Server-side JWTs for Supabase and custom integrations

Since we launched SSR, a frequent request has been to add support for retrieving Supabase tokens during SSR. Today, we launched the capability for Supabase and more!

Support for every JWT template has been added to our server-side Javascript packages for Next.js, Remix, and Express. Simply call getToken({template: "supabase"}) on the new server-side auth context.

Documentation has been added to our SSR beta documentation. You will need to upgrade to the latest version.

Thanks to the contributors: Nikos Douvlis, Peter Perlepes, Haris Chaniotakis, Agis Anastasopoulos

Firebase Authentication user and password migrations

Developers who currently use Firebase Authentication can now migrate users and their passwords to Clerk!

Our backend Create User endpoint has added support for Firebase's special flavor of scrypt so users can easily be migrated to Clerk.

Thanks to the contributors: Alex Ntousias

Toggleable hosted components

Any developer who wants to disable Clerk-hosted components on the accounts subdomain can now do so by contacting support. This option will be made available in our dashboard soon.

Thanks to the contributors: Sokratis Vidros

Community spotlight: Slapdash plugin

Many thanks to Anish De, who created a Slapdash commands plugin that brings Clerk's documentation right to your fingertips.

Thank you, Anish!

Remix Relaunch

Today we relaunched our @clerk/remix package. This includes two key improvements since the initial launch:

1. Applications can now require authentication on a route-by-route basis, instead of requiring authentication for the entire application
2. In development, environment variables can now be set more easily in the Remix-native .env file.

Our documentation has been updated to reflect the improvements. Thank you to our early beta testers who helped test and ideate!

Thanks to the contributors: Nikos Douvlis

Authentication settings refactor

We rolled out a multi-month refactor of our authentication settings to support a new wave of features. It will enable:

• Custom fields
• Profile data collection with web3 auth
• Guaranteed email collection for Twitter OAuth
• A universal auth endpoint (sign up OR sign in)

In the past, our "sign up" simply ensured the user will be able to sign in again. Now, we will be able to add app-specific requirements to sign up, so if your application needs an email address and it turns out a Twitter user is missing theirs, we'll be able to collect it during sign up.

These features aren't available yet, but this infrastructure change will enable us to add them much more quickly.

Thanks to the contributors: Giannis Katsanos, Nikos Petridis, Alex Ntousias, Sokratis Vidros

JWT Templates Launch (GA)

After a few months of testing, we pulled the "beta" label off our JWT templates feature and released to general availability.

We've now generated millions of JWTs and are confident our infrastructure is secure, fast, and robust.

You are free to design custom JWTs for your own application, or leverage our prebuilt templates for common integrations.

Thanks to the contributors: Mark Pitsilos, Agis Anastasopoulos, Haris Chaniotakis

Organization management API

Today we launched our API for organization management and began rolling it out to our early access customers.

Want to see how it works? Check out our demo repository on Github.

These API endpoints are production ready - please reach out to support if you would like early access.

Please note that we do not provide UIs for this functionality yet, but hooks and javascript helpers are available. The demo repository is unstyled but filled with essential organization management features:

Thanks to the contributors: Alex Ntousias, Giannis Katsanos, Peter Perlepes

Custom Scopes for OAuth / Social Login

Clerk now supports custom scopes for OAuth / Social Login. Simply navigate to the "Social Login" page in your dashboard and select the Gear icon for any provider.

By default, Clerk requests the scopes necessary to retrieve any basic profile information for your user. Now, you can add any scope your application needs. For example, the "repo" scope from Github

To retrieve the access token for the third party API, you can use Clerk's backend API.

Thanks to the contributors: Agis Anastasopoulos, Mark Pitsilos

application/json support

Clerk's Backend API now supports request bodies encoded with application/json, in addition to form-encoding. This is in response to developer requests and a growing ecosystem of json tooling.

This feature is automatically enabled for all applications.

Thanks to the contributors: Haris Chaniotakis

Social Login with Microsoft & Notion

Microsoft and Notion have been added to our ever-growing list of Social Login providers. If you need support for one that isn't listed, please reach out to support.

Next up is Apple!

Thanks to the contributors: Mark Pitsilos, Haris Chaniotakis

New FaunaDB JWT template

We've added a prebuilt JWT template for Fauna to improve our integration.

Check out our Fauna guide to get started!

Thanks to the contributors: Agis Anastasopoulos

New feedback form in Dashboard

Have feedback while browsing our Dashboard? Now you can easily send it straight to the Clerk team by clicking the "Give feedback" button in the dashboard.

We're tremendously grateful for any feedback that comes through and we're happy to make it easier than ever.

Thanks to the contributors: Marcel Cruz

Testimonial cloud

Since our launch, we've been fortunate to receive some great testimonials from builders all throughout the Javascript community. Today, we launched an update to begin featuring these on our homepage.

Thanks to the contributors: Charles Wefso, Cooper Dawson

Redwood guide

We've had a chance to connect more closely with the Redwood team and our integration experience is rapidly improving.

After launching a tutorial two weeks ago, we heard a lot of feedback that we were missing our standard integration docs. Those docs are now live.

Thanks to the contributors: Ian McPhail

Remix new SDK and guide

Our beta for Remix continues! After receiving a few bug reports and great ideas for improvements, we launched a new version of the SDK today.

We also put together a new Getting Started guide so developers no longer need to reverse-engineer our demo repository.

Thanks to the contributors: Nikos Douvlis, Colin Sidoti

The Organization object is coming soon!

At Clerk, we've always wanted to help developers with Customer Management, not just User Management. Depending on your business, you might sell to Users (B2C) or Organizations (B2B).

Starting late next week, we'll begin rolling out support for a Clerk-managed Organization object. The launch will start with frontend APIs first, including:

• An API to create an organization
• An API to invite other users to the organization
• An API to set users roles within the organization

The organization(s) that a user is part of will become part of their short-lived session JWT, so Clerk will start assisting with "authorization" in addition to "authentication."

This is just the beginning of Organization management at Clerk. Ultimately, we expect about half of our team to be focused solely on Organization management this year - including to build common requests like component UIs, SAML authentication, and subscription management. Stay tuned :)

If you would like to be included in the beta, please contact support

Thanks to the contributors: Alex Ntousias, Giannis Katsanos, Peter Perlepes, Nikos Petridis, Shawn Winters, Rishi Raman, Braden Sidoti, Colin Sidoti