PhoenixKit
v{Application.spec(:phoenix_kit, :vsn)}
<%!-- User info display - shows how to access user data in layouts --%>
<%!-- Scope-based authentication (recommended approach) --%>
<%= if assigns[:phoenix_kit_current_scope] && PhoenixKit.Users.Auth.Scope.authenticated?(@phoenix_kit_current_scope) do %>
Logged in as: {PhoenixKit.Users.Auth.Scope.user_email(@phoenix_kit_current_scope)}
<% else %>
Not authenticated
<% end %>
<%!--
Legacy option: Basic user check (backwards compatibility)
If you're still using :phoenix_kit_mount_current_user, this approach works:
<%= if @phoenix_kit_current_user do %>
Logged in as: {@phoenix_kit_current_user.email}
<% else %>
Not authenticated
<% end %>
To use scope approach, update your router:
live_session :default,
layout: {MyAppWeb.Layouts, :app},
on_mount: [{PhoenixKitWeb.Users.Auth, :phoenix_kit_mount_current_scope}] do
# your routes
end
Benefits of scope approach:
- Better encapsulation of authentication state
- Explicit authentication checks
- Ready for future extensions (roles, permissions, etc.)
- Type safety with proper struct
--%>