Changelog

Apr 2

Clerk Billing now supports plans with seat limits

Category: Billing
Published: Apr 2

Include seat limits in your organization billing plans

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.

A pricing table for 3 different plans, with different seat limits on each plan

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.

A disabled invitation button with a message indicating the user needs to upgrade their plan.

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.

Mar 27

Overview for waitlist mode

Category: Dashboard
Published: Mar 27

The Overview page now has a dedicated waitlist view so it's easier to understand sign-up access and recent waitlist activity.

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.

Mar 26

Clerk is now available in Stripe Projects

Category: Product
Published: Mar 26

Add authentication and user management to your app through Stripe Projects with a CLI-based workflow for teams and AI agents.

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:

stripe plugin install projects
stripe projects init my-app
stripe projects add clerk

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

Mar 16

Organization activity report

Category: Dashboard
Published: Mar 16

Visualize how active each organization is in your application

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.

Mar 9

Create and manage enterprise connections through Clerk's API

Category: API
Published: Mar 9

Create, list, read, update, and delete enterprise connections programmatically.

You can now fully manage both SAML and OIDC enterprise connections via the Clerk Backend API. Previously, you could only manage SAML connections via the API.

What's new

The following endpoints are now available on Clerk's backend API:

Method	Path	Description
`POST`	`/v1/enterprise_connections`	Create an enterprise connection. Accepts `provider`, `domains`, `name` and `organization_id` as params
`GET`	`/v1/enterprise_connections`	List enterprise connections. Query: `organization_id` (optional), pagination.
`GET`	`/v1/enterprise_connections/{enterpriseConnectionID}`	Get a single enterprise connection.
`PATCH`	`/v1/enterprise_connections/{enterpriseConnectionID}`	Update an enterprise connection.
`DELETE`	`/v1/enterprise_connections/{enterpriseConnectionID}`	Delete an enterprise connection.

If you currently use the /saml_connections endpoint, we recommend migrating to the new /enterprise_connections endpoint. This unified API allows you to manage both SAML and OIDC connections, and will serve as the primary interface moving forward. Support for the legacy SAML endpoint may be phased out in the future.

Getting started

Visit the API reference for detailed documentation on request parameters and response formats.

Mar 9

Native React Native components, Google Sign-In, and Core 3

Category: SDK
Published: Mar 9

@clerk/expo now ships prebuilt native components (AuthView, UserButton, UserProfileView), native Google Sign-In, and Core-3 Signal APIs.

@clerk/expo 3.1 brings native UI components powered by SwiftUI (iOS) and Jetpack Compose (Android), native Google Sign-In, and the new Core-3 Signal API. This is a major version bump that requires Expo SDK 53+.

Native React Native components

Three prebuilt native components are now available from @clerk/expo/native:

<AuthView /> renders the full sign-in/sign-up UI natively, with support for signIn, signUp, and signInOrUp modes. Session sync to the JS SDK happens automatically.
<UserButton /> displays the user's avatar and opens the native profile modal on tap. It fills its parent container, so the parent controls the size and shape.
<UserProfileView /> renders the profile management UI inline. For modal presentation, use the new useUserProfileModal() hook.

All components use hook-based state management rather than callbacks. React to auth state changes with useAuth() in a useEffect:

import { AuthView, UserButton } from '@clerk/expo/native'
import { useAuth, useUserProfileModal } from '@clerk/expo'

function App() {
  const { isSignedIn } = useAuth()
  const { presentUserProfile } = useUserProfileModal()

  if (!isSignedIn) {
    return <AuthView mode="signInOrUp" />
  }

  return (
    <>
      <View style={{ width: 44, height: 44, borderRadius: 22, overflow: 'hidden' }}>
        <UserButton />
      </View>
      <TouchableOpacity onPress={presentUserProfile}>
        <Text>Manage Profile</Text>
      </TouchableOpacity>
    </>
  )
}

These components require the @clerk/expo Expo config plugin, which automatically adds the clerk-ios and clerk-android native SDKs to your project. See the native components overview for setup and usage.

Google Sign-In now uses platform-native APIs instead of browser-based OAuth:

iOS: ASAuthorization (system credential picker)
Android: Credential Manager (one-tap / passkey-ready)

This is exposed via the NativeClerkGoogleSignIn TurboModule spec and integrated into the @clerk/expo config plugin. No extra packages are needed beyond configuring your Google OAuth credentials in the Clerk Dashboard.

Core-3 Signal APIs

@clerk/expo 3.1 ships with the Core-3 Signal API, which replaces the legacy setActive() pattern with reactive hooks:

// Core 3
const { signIn } = useSignIn()
await signIn.create({ identifier: email })
await signIn.password({ password })
if (signIn.status === 'complete') {
  await signIn.finalize({ navigate: () => router.push('/') })
}

Key changes from Core 2:

signIn.password(), signIn.emailCode.sendCode() replace signIn.attemptFirstFactor()
signIn.finalize() replaces setActive({ session: signIn.createdSessionId })
Error handling via errors.fields.identifier?.message instead of try/catch

See the Expo quickstart and Core-3 upgrade guide for migration details.

New hooks

Three new hooks are exported from @clerk/expo:

Hook	Description
`useUserProfileModal()`	Present the native profile modal imperatively. Returns `{ presentUserProfile, isAvailable }`.
`useNativeSession()`	Access native SDK session state: `isSignedIn`, `sessionId`, `user`, `refresh()`.
`useNativeAuthEvents()`	Listen for auth state changes (`signedIn`, `signedOut`) from native components.

Get started

Follow the Expo quickstart to set up a new project with native components, or check the native components reference for the full API. The clerk-expo-quickstart repo has three example apps: JS-only, JS with native sign-in, and full native components.

Clerk Changelog