Clerk Changelog

Clerk's native mobile SDKs now include prebuilt Organization management UI for iOS and Android. These views cover account switching and Organization settings.

What's new

• OrganizationSwitcher renders the active Organization or personal account, then opens native controls for switching accounts, accepting invitations and suggestions, creating Organizations, and managing the active Organization.
• OrganizationListView provides a standalone account picker for selecting a personal account or Organization, including memberships, invitations, suggestions, and Organization creation when available.
• OrganizationProfileView renders permission-gated Organization management for profile details, members, invitations, requests, verified domains, leaving Organizations, and deleting Organizations.

Email Logs are now available in public beta for production instances. The new Email Logs⁠ page in the Clerk Dashboard gives you a reverse-chronological view of transactional email delivery events, so you can debug delivery issues without leaving the Dashboard.

Use Email Logs to understand what happened to an email after Clerk sent it, including whether the receiving mail service accepted it, whether delivery was delayed or failed, and whether the user opened or clicked it. You can filter logs by recipient email address, IP address, message ID, time range, and event type.

Select any log entry to view its details, including delivery status, response or bounce reason, related metadata, and the original provider payload when available.

Get started

Open Email Logs⁠ from the Logs section of the Clerk Dashboard. For workspaces using custom roles and permissions, grant the Email logs read permission to the roles that should have access.

The Orgs tab of your Overview page now includes a report stack ranking the largest organizations in your instance by current member count.

• Top organizations at a glance: See your biggest orgs in descending order with member counts, and a link to each organization's detail page.
• Visual size comparison: Each org is rendered as a bar scaled to its member count, making it easy to see how your top orgs stack up against each other.
• Spot outliers and growth: See how usage is distributed across your tenants and catch unusual growth patterns.

Open the Clerk Dashboard⁠ and head to the Overview page to view your largest organizations.

Available now for all instances with organizations enabled.

A new elevation appearance option lets you control whether page-mounted Clerk components render inside a card (raised) or directly on the page (flush). The default is raised, preserving existing behavior.

<SignIn
  appearance={{
    options: {
      elevation: 'flush',
    },
  }}
/>

When set to flush, components drop their card background, border, and shadow, making it easier to embed sign-in, and sign-up components into your own layouts. Modals and popovers always use raised regardless of this setting.

See the appearance options documentation for more details.

Groups and custom attributes mapping are now generally available, completing the Directory Sync (SCIM) GA rollout that began with the core provisioning release. Both features are enabled for all users with no extra configuration required.

• Groups mapping assigns Clerk roles automatically based on IdP group membership. When a user is added to a group in your IdP, Clerk applies the mapped role. When they're removed, they fall back to the next mapped role. For users in multiple groups with different role mappings, a configurable precedence order controls which role wins.

• Custom attributes mapping syncs additional user data from your IdP (such as department, employee_id, or cost_center) directly into publicMetadata on the Clerk user object. Attribute definitions are configured once at the enterprise connection level and shared across both your SSO connection (SAML or OIDC) and your Directory Sync connection, so the same attributes are available regardless of how a user authenticates or is provisioned. When Directory Sync is enabled, it becomes the exclusive source for those attribute values and they're read-only in Clerk until Directory Sync is disabled.

Getting started

To enable Directory Sync, navigate to an enterprise connection in the Clerk Dashboard⁠, open the Directory Sync tab, and toggle it on. Clerk generates a SCIM base URL and bearer token to configure in your IdP.

Refer to the Directory Sync documentation for setup guides, the Role mapping documentation for groups-to-role configuration, and the Custom attribute mapping documentation for details on the shared attribute pool.

Pricing

Directory Sync, including groups and custom attributes mapping, is included with your enterprise connection at no extra charge. Refer to the pricing page for connection pricing details.

OAuth Applications now integrate with Clerk Organizations. When your instance has Organizations enabled, users going through the OAuth flow can select which organization they're acting on behalf of, and the OAuth client receives that selection as an org_id claim on the access token.

How it works

We've added a new user:org:read scope to OAuth Applications. When a client requests this scope and the user grants it, the OAuth consent screen displays an organization selector. After consent, the access token issued to the client includes an org_id claim populated with the selected organization.

If the consent screen is disabled for your OAuth Application, org_id is populated with the user's last active organization instead.

For convenience, the userinfo endpoint also returns org_name and org_slug alongside org_id, so clients can display organization context without an extra lookup.

Enabling it on an existing OAuth Application

Updating an existing OAuth Application is as simple as enabling the new user:org:read scope in its settings on the Clerk Dashboard⁠. No other changes are required — once the scope is available, clients can request it on their next authorization request.

To learn more, see our OAuth Applications documentation.