Dashboard

The tenant dashboard is the landing page for an active organization at /{orgSlug}. It is the place for "what needs your attention" rather than a duplicate navigation hub.

Current Scope

The dashboard is organization-scoped and runs behind the same organization access guard as the rest of the tenant app. It should only show data the current user can access through their organization permissions.

Recent activity

The Recent activity timeline is the same user-scoped notifications inbox as the topbar bell: mentions, assignments, inbound Inbox reply-needed items, approvals, running work, and failures. Rows link to the subject (/tasks/…, /inbox/…, /chats/…, /workflows/…/runs/…) and use the same originator avatar + type badge as /notifications. Pending-action rows can show a secondary Review or Reply link.

Intended Aggregations

The product direction is to aggregate:

• Tasks that are due, blocked, or assigned to the user.
• Inbox messages and unread communication.
• Workflow alerts and failed automations.
• Notifications and mentions (the timeline already uses this inbox).
• Billing or usage warnings when the user can manage billing.

Design Principle

Dashboard cards should link to the owning detail/list pages. Avoid adding one-off dashboard-only data contracts when the underlying module already has a service method or table route.