Default dashboard governance

DEFAULT DASHBOARD:
  - One per org
  - Set by anyone with the dashboard:update policy (Admin and
    Editor by default)
  - Stored as the default_dashboard key in org_settings
  - Value: either a preset key (executive / engineering / finops /
           all_widgets) OR a UUID of a saved customized dashboard

USERS LAND ON THE DEFAULT when:
  - First sign-in (no bookmark yet)
  - Navigating to /dashboard without a specific dashboard URL
  - Bookmark not set

PROCESS:
  1. Open Dashboards page
  2. Pick any preset or any saved dashboard
  3. Click "Set as org default" (needs dashboard:update)
  4. Confirm the change
  5. All users now land on the new default

REQUIRES:
  The dashboard:update policy: Admin and Editor have it
  by default, or a custom role with the policy

EFFECT:
  Immediate. Next /dashboard visit picks up the new default.

EVERY CHANGE IS AUDITED:
  - Who changed it
  - When
  - The new default (the entry stores the request, so it
    shows the new dashboard, not the one it replaced)
  - The change appears in M4.3 audit log

EASY TO REVERT:
  If the new default causes confusion (users complain, or new
  joiners report disorientation), revert to the previous in 30 seconds.

NO USER-DATA IMPACT:
  Changing the default does not delete other saved dashboards.
  Users' bookmarks remain pointing at their preferred dashboards.

DEFAULT DOES NOT:
  Lock users to the dashboard          → users can switch
  Prevent users from switching         → header switcher always works
  Force users to view it every visit   → personal bookmarks override
  Hide other dashboards                 → all saved dashboards visible
  Affect per-user customization         → not supported in V1 anyway
  Apply different defaults per role     → one default for the whole org

USERS RETAIN FLEXIBILITY:
  Switch dashboard via header switcher
  Bookmark a different one as their personal landing
  Navigate directly via URL
  Visit any saved dashboard

PATTERN A: All Widgets (out of the box)
  System default for new orgs.
  Best for: orgs early in the evaluation, mixed needs.
  Transition path: as the team matures, switch to a focused preset.

PATTERN B: FinOps preset
  Best for: orgs with a dedicated FinOps practice.
  A common choice for mature FinOps practices.

PATTERN C: Executive preset
  Best for: orgs where leadership drives the cost conversation.
  Common in finance-led orgs.

PATTERN D: Custom cloned dashboard
  Best for: orgs with specific needs not covered by presets.
  Common after 6-12 months of ZopNight use; reflects accumulated
  learning about what matters to the team.

ORG DEFAULT:     The FinOps preset (org's primary landing)
USER BOOKMARKS:
  - FinOps Lead's bookmark: FinOps preset (same as default)
  - Engineering Lead's bookmark: Engineering preset
  - Executive's bookmark: Executive preset
  - Junior engineer's bookmark: Engineering preset

NEW JOINER:
  Lands on org default (FinOps preset) on first sign-in
  Explores; discovers Engineering preset; bookmarks it
  Subsequent visits go to Engineering preset (their bookmark)

RESULT:
  Each user's experience is personalized; org maintains a sensible
  default for newcomers.

IF THE ORG IS DELETED (rare):
  The default_dashboard pointer is cleared
  No orphaned configuration in the database

IF THE DEFAULT DASHBOARD IS DELETED:
  In the UI: the delete is blocked ("Reassign default first")
  Through the API or MCP: the delete succeeds, the pointer is
  cleared, and the org falls back to the All Widgets preset

IF A USER'S BOOKMARKED DASHBOARD IS DELETED:
  Bookmarks are browser links to /dashboard/<id>; ZopNight
  does not store them
  Opening the link shows "Dashboard not found"
  The user re-bookmarks, or opens /dashboard for the org default

GOOD REASONS TO CHANGE:
  - Org evolves from generic to specific (All Widgets → FinOps preset)
  - Audience focus shifts (engineering-led → leadership-led)
  - Team feedback shows people land on wrong dashboard
  - New custom dashboard is built and validated

BAD REASONS:
  - Individual preference (use a bookmark instead)
  - Trying to "force" everyone to use a specific view (V1
    doesn't lock users; they'll just bookmark something else)
  - Frequent experimentation (creates churn; pick one and commit
    for a quarter)

CADENCE:
  Quarterly review is typical
  Annual review for stable orgs
  Each change documented in team wiki with rationale

ORG: Acme Corp; new ZopNight customer
TIMELINE:

T+0 (onboarding day):
  Default: "All Widgets" (system default)
  Audience: new ZopNight users exploring everything

T+1 week:
  Admin notices the team mostly uses the FinOps surfaces
  Switches default to "FinOps preset"
  Audit log records the change with the new default,
  "finops" (the entry does not store the old one)

T+1 month:
  Admin clones FinOps preset to "FinOps Acme Daily"
  Modifications:
    Removed "Scheduler success rate" (not used)
    Added "Showback" (team wants team and tag split up front)
    Reordered to put Cost reports first
  Sets the clone as default

T+3 months:
  Some users have bookmarked different views:
    Engineering team → Engineering preset
    CFO → Executive preset
    Compliance → custom "Audit Review" dashboard
  Each user lands on their bookmark
  New joiners still land on "FinOps Acme Daily"

T+6 months:
  Admin reviews; "FinOps Acme Daily" is still the right default
  Documents the rationale in team wiki

T+9 months:
  Executive leadership wants their own focused dashboard
  Admin clones Executive preset → "Acme Monthly Review"
  Does NOT set as default (org-wide default remains FinOps-focused)
  CFO + execs bookmark "Acme Monthly Review"

T+1 year:
  Stable. Default is FinOps Acme Daily. Personal bookmarks per audience.
  Quarterly review confirms current default is right.

CURRENT ORG DEFAULT:    __________

IS THIS THE RIGHT DEFAULT for your org?
  □ Yes: it matches the most-common audience's needs
  □ Maybe: has been default a while; review needed
  □ No: should change to: __________

YOUR PERSONAL BOOKMARK:
  Current bookmark:    __________
  Matches default?     Yes / No
  If no: that's normal; bookmarks are personal preferences

QUARTERLY REVIEW DATE: __________
  Set a calendar reminder to re-evaluate the default

DOCUMENTATION:
  Is the default + rationale documented in team wiki? Yes / No