Clerk Changelog

Understand how well your application retains organizations with the new organization retention report. Clerk automatically tracks how many organizations remain active after creation, enabling you to visualize how your organization retention is trending versus industry benchmarks.

Features

• Change the interval to see how your organization cohorts retain over the first 30 days, 8 weeks, and 3 months.
• Visualize how your retention is changing over time by comparing the last three or six cohorts.
• Set a goal shape to measure how your retention is improving towards industry benchmarks.
• View recent cohorts in progress, or toggle off 'show incomplete period' to see only cohorts with complete data.

You can now require multi-factor authentication (MFA) across your iOS and Android authentication flows with a single toggle.

This applies to both new users during sign-up and existing users when they sign in, ensuring MFA is completed before access is granted.

What's new

Requiring multi-factor authentication (MFA) now works end-to-end in prebuilt authentication flows for iOS and Android.

If a session is created in a pending state with a setup-mfa task, the SDK automatically routes users to the dedicated MFA setup flow instead of completing sign-in. Users can set up one of your enabled MFA methods, including Authenticator app (TOTP) and SMS verification code.

Getting started

To require MFA in your mobile application:

1. Navigate to Multi-factor⁠ in the Clerk Dashboard.
2. Enable one or more MFA strategies (Authenticator app or SMS verification code).
3. Turn on Require multi-factor authentication.

Once enabled, new users are prompted to set up MFA during sign-up, and existing users without MFA are prompted the next time they sign in.

To learn more, visit the setup MFA guide⁠.

What's new

• Shareable test URLs — From any enterprise connection (SAML or OIDC) in the Dashboard, use Copy Test URL to generate a one-time link. Share it with your customer or IT team so they can run a sign-in attempt against your connection.

• Test logs — Results of each test URL run (success or failure and details), so you can get more information for troubleshooting.

Getting started

In the Clerk Dashboard⁠, go to User authentication → SSO connections, open an enterprise connection, and complete the connection setup. Then use Copy Test URL to create and copy a test link. Share it with your customer to run a test sign-in; the attempt will appear under Test logs.

These libraries connect Clerk authentication with Convex clients, keeping auth state in sync without requiring custom token handling.

For integration and configuration details, refer to the following repositories:

• clerk-convex-swift⁠
• clerk-convex-kotlin⁠

Each repository includes example apps and setup instructions.

Securing your user base even more just got a lot easier. You can now require multi-factor authentication (MFA) across your entire application with a single toggle.

This ensures that every user, whether they are signing up for the first time or returning to an existing account, adds a critical layer of protection before they can access your application.

What's new

The require multi-factor authentication (MFA) setting eliminates the "opt-in" gap. Previously, users had to manually choose to secure their accounts. Now you can make it a requirement for entry.

If a user signs-in or signs-up without multi-factor authentication (MFA) enabled, they’ll be guided through the setup flow before proceeding.

This works seamlessly with Clerk’s prebuilt components. Users can choose from the available application MFA methods, including Authenticator application (TOTP) and SMS verification code.

Getting started

To require multi-factor authentication (MFA) across your application:

1. Ensure your Clerk SDKs meet the minimum required versions. Refer to the setup-mfa session task guide⁠ for version requirements.
2. Navigate to Multi-factor⁠ in the Clerk Dashboard
3. Enable one or more MFA strategies (Authenticator application or SMS verification code).
4. Turn on Require multi-factor authentication

Once enabled, new users will be prompted to set up MFA during sign-up, and existing users without MFA will be prompted the next time they sign-in.

To learn more, visit the setup MFA guide⁠.

• Proactive alerts are now available. A warning icon and banner appear when Stripe reports outstanding account requirements.

• Issues can be resolved directly from the Dashboard. Clicking the warning banner opens Stripe so you can complete required items.

• Warnings are visible in key billing areas. They appear in the Billing tab and in Billing settings under the Configure section.

• Early resolution helps prevent payment interruptions for Clerk Billing.