# `PhoenixKitWeb.Live.Dashboard` [🔗](https://github.com/BeamLabEU/phoenix_kit/blob/v2.14.2/lib/phoenix_kit_web/live/dashboard.ex#L1) The `/admin` landing page. It is built to be the page ANY authenticated visitor can safely be sent to, whatever their permissions. Two halves: * a **welcome block**, rendered for everyone, greeting the visitor by name; * the **operator overview** (`PhoenixKitWeb.Components.Core.DashboardOverview`), every block of which is permission-gated by `PhoenixKitWeb.Live.Dashboard.Overview`. A visitor holding no permissions sees the welcome block and nothing else — no statistics, no System Information, no cards, and (because the overview decides before it queries) not one operator query or PubSub subscription on their behalf. That is what makes the page safe as a universal landing. Reaching it is not the same as being allowed to see all of it. The route sits in the ordinary admin `live_session`, alongside every other `/admin/*` page, so admin navigation to and from it stays a live patch rather than a full page reload. What admits a permission-less visitor is the GATE: `:phoenix_kit_ensure_admin` recognises this view via `PhoenixKitWeb.Users.Auth.landing_view?/1` and skips the admin-area and per-view permission checks for it alone — authentication, the account gate and the locale hook still run. The overview's own gates are what keep the operator blocks away from whoever gets in. Because nobody is ever evicted from this page, it has to survive a permission change in place: `PhoenixKitWeb.Users.Auth`'s scope-refresh hook skips its eviction for the landing view and instead calls `phoenix_kit_scope_changed/1`, which re-runs `PhoenixKitWeb.Live.Dashboard.Overview.assign_scope_gates/1`. A demoted operator watches the cards and statistics disappear (and the subscriptions behind them close) without leaving the page or reloading it. `/dashboard` is a SEPARATE page (`PhoenixKitWeb.Live.Dashboard.Index`), deprecated since 2026-07-27 and sharing nothing with this one. # `render` # `welcome_block` The welcome half of `/admin` — the part with no permission gate at all, and therefore the whole page for a visitor holding nothing. Deliberately an `

`, not an `

`: the page's one header is the `LayoutWrapper` breadcrumb, and this sits at the same level as the operator overview's own section headings. The greeting is a key resolved through `greeting_text/1`, whose clauses are literal `gettext/1` calls — new phrases fall back to English until locales catch up, `"Welcome back"` stays translated everywhere. The name is appended in markup rather than interpolated into a `"…, %{name}"` msgid, which would ship untranslated everywhere. It is a function component rather than mount assigns so that `gettext` runs at RENDER time: a locale switch that only patches params (`handle_params`, after mount) still reaches it. Greeting and name render inside ONE child element: `card-title` is a flex container with a gap, and as sibling flex items the phrase and the `, name` span drew that gap between the phrase and the comma. ## Attributes * `scope` (`:any`) (required) - the visitor's `PhoenixKit.Users.Auth.Scope`, or `nil`. * `greeting` (`:atom`) - greeting key drawn once per mount — see `pick_greeting/1`. Defaults to `:welcome_back`. --- *Consult [api-reference.md](api-reference.md) for complete listing*