Dashboard visibility requires a separate, undocumented 'createDashboard' mutation not obvious from the page layout creation flow

[fcporto-nature]

Summary

Problem
Building a dashboard by creating 'pageLayout'/'pageLayoutTab'/'pageLayoutWidget' records (directly or by copying an existing example) produces no visible or listed dashboard in the UI, with no error raised anywhere. The missing piece is a separate 'dashboard' object record (a distinct entity with just a title and a pageLayoutId) that must be created via its own 'createDashboard' mutation — this is not mentioned in the page layout documentation and is easy to miss entirely.

Proposed solution
Document the relationship between page layouts and the 'dashboard' object clearly in the dashboards/page-layouts documentation, and/or surface a warning in the UI or API when a page layout of dashboard type exists without a corresponding dashboard record.

Additional context
Several hours were spent troubleshooting a dashboard that had correct underlying data but never appeared anywhere, before finding the missing 'dashboard' record requirement. With GraphQL introspection disabled by default on self-hosted instances, this kind of gap is especially costly to diagnose.

---

This feature idea was drafted with AI assistance as part of an internal improvement-tracking workflow. It is a suggestion only — no code changes are proposed or included.