Favorites & pins
Edition: favorites, pins, and the curated home page are Enterprise Edition features. The Developer Edition is a single-user local runtime and does not include them.
Two independent ways to surface the dashboards that matter: favorites are personal, pins are curated for everyone. On the home page, dashboards are grouped so the most relevant ones are easiest to reach — pinned first, then your favorites, then your recents.
Favorites (per user)
A favorite is personal to you. Open a dashboard and toggle the star in the dashboard controls — solid means favorited, outline means not. Your favorites are collected on the home page so you can jump back to the dashboards you use most, without affecting what anyone else sees.
Favorites are a convenience layer only: they change ordering and discovery, never who is allowed to open a dashboard (that is governed by RBAC). Favoriting is available to any signed-in user. (An Enable favorites switch appears in the admin console, but it is reserved — favorites are currently always available in the runtime.)
Pins (admin-curated, global)
A pin is global and curated by an administrator. Pinned dashboards are the ones an organization wants everyone to see first — a company KPI board, an onboarding dashboard — and they appear above favorites and recents on the home page for all users.
Pinning is an admin action, managed from the Pins tab of the admin console: pick a dashboard and Pin it (or Unpin to remove). Unlike a favorite, a pin is not tied to one person — it curates the shared home page.
How pins relate to the git registry
Pins and the git registry are independent — a dashboard can be pinned without being version-controlled, and vice versa — but they interact in one place: **deregistering a pinned dashboard from git is an admin-only action.** The per-dashboard git toggle will not remove a pinned dashboard from version control; an administrator must do it from the Pins tab ("Git registry — admin override"). This protects curated, surfaced dashboards from being pulled out of version control by accident. Ordinary (non-pinned) dashboards can be deregistered by any user with the git toggle. See Dashboards as code.
At a glance
| Favorite | Pin | |
|---|---|---|
| Scope | Personal to one user | Global, all users |
| Who sets it | Any signed-in user | Administrator only |
| Where | Star in the dashboard controls | Admin console → Pins |
| Home-page order | After pins, before recents | First, above everything |
| Governs access? | No — discovery only | No — discovery only |
Shaleio