Feature: allow setting a Dashboard as the default landing page (post-login home)

[richroberts-prog]

Problem

Twenty currently has no way to set a Dashboard as the post-login landing page. The default routing logic in useDefaultHomePagePath.ts only considers object table views:

1. lastVisitedObjectMetadataItemId (client-side Jotai state) → that object's table
2. Else, the alphabetically-first readable non-system object (typically "Companies")

Dashboards are not considered, even though Twenty's Dashboard primitive (with multi-tab support + RECORD_TABLE / chart widgets) is exactly the surface most CRM users want as their home.

Use case (concrete)

We're a self-hosted Twenty workspace running EOS (Entrepreneurial Operating System). Our Today dashboard contains four tabs:

• Tab 1 — Rocks (current quarter)
• Tab 2 — Tasks (assigned to me)
• Tab 3 — Issues (open IDS items)
• Tab 4 — Meetings (recent CouncilSessions)

This is the workspace member's daily homepage. We want it to be where users land after sign-in or when explicitly navigating "home". Today users have to either bookmark the dashboard URL or click through Favorites.

Why this fits Twenty's architecture

• The Dashboard object already exists with multi-tab/multi-widget support (gh#20006 et al.).
• `WorkspaceMember.settings` is already an opaque JSON column with an existing `updateWorkspaceMemberSettings` mutation — adding a `homePageDashboardId` key is non-breaking.
• The default-home logic is contained in one hook (`useDefaultHomePagePath.ts`).

Proposed shape

1. Add a recognised key to `WorkspaceMember.settings`:

```ts
type WorkspaceMemberSettings = {
// ... existing keys (locale, timeZone, colorScheme, ...)
homePageDashboardId?: string; // UUID of a Dashboard the user owns or can read
};
```

2. Update `useDefaultHomePagePath.ts`: before the existing `lastVisitedObjectMetadataItemId` branch, check whether `currentWorkspaceMember.settings.homePageDashboardId` is set and the dashboard is still readable. If yes → return `/object/dashboard/`.

3. Surface it in Settings UI: add a "Home page" field under Settings → Profile that lets a user pick any Dashboard they have access to (or revert to "Last visited object").

Acceptance criteria

• Setting `homePageDashboardId` via `updateWorkspaceMemberSettings` causes the user to land on that dashboard after sign-in / on `AppPath.Index`.
• Clearing the setting falls back to current behaviour.
• Setting it to a deleted/unreadable dashboard falls back gracefully without redirect loops.
• Per-user, not workspace-wide (different users may want different dashboards).

Workarounds we're using meanwhile

1. Adding the dashboard to Favorites (one click from any page).
2. A bookmark to the dashboard URL.

Both work, but neither is the home page in any meaningful sense.

Related

• PR Change defaultHomePagePath from /objects/companies to last visited page #6612 — `Change defaultHomePagePath from /objects/companies to last visited page` (laid the per-user-routing groundwork)
• PR Fix orphan views by deferring record table widget view creation to dashboard save #20006 — `Fix orphan views by deferring record table widget view creation to dashboard save` (related dashboard infra)

Happy to open a PR if the team confirms this shape is acceptable.

[Diimiitroof]

+1 — would love to see this. We run a small self-hosted Twenty workspace for our business, and this would be genuinely useful. Bookmarking the dashboard URL works as a workaround, but a proper default landing page would make a real difference in daily use.

[BOHEUS]

@richroberts-prog you can have a specific dashboard visible after logging in if you set it first in navigation menu