user-access

Use the useAuth() hook in client components to access user.id, and read context.userId from ApiHandlerContext in server API handlers to retrieve the authenticated user ID for authorization and personalization.

Call useAuth() in your client component to access the user object for conditional rendering; it returns user data when authenticated and undefined when unauthenticated, enabling personalized UI based on JWT authentication status.

Access context.userId from ApiHandlerContext in your server API handler and guard the route by returning an error or redirecting when userId is undefined, ensuring only authenticated users can reach protected data endpoints.

Yes, JWT-derived userId is available in ApiHandlerContext on the server, allowing you to authorize requests, enforce user-based access control, and fetch user-specific data securely in your API handlers.

useAuth returns undefined for unauthenticated users because no valid JWT session exists, allowing client code to distinguish between logged-in and logged-out states for conditional rendering and personalized UI decisions.

No separate library is needed if you have a client-side useAuth hook exposing user.id and a server-side ApiHandlerContext deriving userId from JWT, as these cover reading authenticated user identity for both UI personalization and protected data access.