router-core/auth-and-guards

Use a pathless layout route with a beforeLoad guard to verify authentication and call redirect() to send unauthenticated users to the login page, preventing protected child routes from rendering until auth succeeds.

Apply RBAC within the beforeLoad guard by checking user roles and permissions, then conditionally allow access or redirect. This controls authorization at both page and nested-route levels before rendering.

Use the isRedirect helper to identify and re-throw redirects caught in try/catch blocks during beforeLoad execution, ensuring proper error handling while preserving the intended redirect flow.

Yes. Integrate your auth provider into the RouterProvider context to share authenticated state across the app, enabling consistent access control and redirect-based flows throughout all routes.

Yes. The beforeLoad guard and RouterProvider context integration support external auth providers including Auth0, Clerk, and Supabase to manage authenticated states and redirect-based access flows.

Create a pathless layout route with a beforeLoad guard that enforces authentication and redirects unauthenticated users, automatically protecting all nested child routes under that boundary.