clerk-react-router-patterns

To add Clerk authentication to React Router v7 loaders and actions, configure `clerkMiddleware()` in your root route, call `rootAuthLoader` in the root loader, and use `getAuth(args)` to read user identity inside individual route loaders and actions.

The best way to protect routes in React Router v7 is by checking authentication inside your route loaders using `getAuth(args)`, which allows you to evaluate access control server-side and redirect signed-out users to the sign-in page before HTML is sent.

Clerk handles SSR user data injection by fetching user and organization data during server-side rendering via route loaders, allowing client components to render personalized UI immediately without requiring additional client-side authentication roundtrips.

Yes, you can implement organization switching in React Router v7 by using the `OrganizationSwitcher` component for UI and building org-scoped loaders that read the `orgId` from `getAuth(args)` to load organization-specific data or redirect when missing.

Yes, you need to export `clerkMiddleware()` from your root route to intercept requests and maintain consistent user identity across middleware, loaders, actions, and SSR rendering before passing the auth state down to `rootAuthLoader`.