Dashboard product
The Dashboard product source route is level 0 and mounts when web_dashboard_x is enabled or configuration is loading. Its sidebar item requires the enabled value. This product editor is separate from Settings → Dashboard Customization; neither route or menu state proves deployed availability.
Configure Dashboard Settings
The product editor defines Basic Settings for Name and Description, the Default Domain, custom-domain request/change flow, notification preference, and branding resources. Branding controls include Dashboard images, favicon, title, and button colors.
The Dashboard controller reads sites on mount. If no dashboardweb site exists, or if a matching record needs its code/type normalized, current source can send a site register or update request automatically. Do not open this route in a production project for documentation. No read, mount write, save, domain action, upload, or Dashboard effect was run.
The notification preference chooses between a temporary new-order notification and a persistent notification. Branding resources can affect the Dashboard logo, sign-in background, browser favicon/title, and primary button colors.
The Dashboard variant does not expose the shared website editor's Advanced or Ordering Widgets tabs. Do not copy website widgets or website-only assumptions into Dashboard Settings.
Some branding and notification controls also appear under Settings → Standard → Dashboard Customization. Treat both as project-wide configuration surfaces. Avoid editing the same value from both pages during one change, and verify the final Dashboard and sign-in experience after saving.
Domains and branding
Source UI instructs users to enter a custom domain without a protocol or slash and models pending-validation, issued, error, revoked, cancelled, and expired states. Requesting, changing, or removing a domain and saving branding are persistent effect classes; a response or displayed state is not proof of DNS, certificate, sign-in, or deployed-branding success. Never include credentials, certificates, tokens, or production-domain values in support captures.
Troubleshooting
Why are Advanced or Widgets missing?
They are intentionally omitted for the Dashboard product. Use the controls available in its Basic Settings only.
Why is a custom domain not live?
Check its displayed lifecycle status. A request can remain pending validation or fail; do not treat Save as proof that DNS or SSL is complete.
Related guides: Dashboard customization · My products