Dashboard

Dashboard at /dashboard is the shared operational picture: the tenant’s work at a glance. It reads from the same lists the team works in every day; it does not hold its own separate records.

• The header greets by name with view tabs and a Customize action. Scope filters sit beneath: work scope, organization, due date, and company.
• Cards summarize the near term: tasks and deliverables due next 7 days, open approvals with trend, and a Status Distribution donut.
• The Activity Feed narrates recent approval requests with requester and age. The feed tells you where attention goes; the lists tell you what to do about it.

• Read the dashboard before the day starts, not after it ends.
• What the dashboard shows is governed by saved views. Create a public view on a list page, then set the org default under Table Views. A wrong default re-trains everyone at once.
• A number that surprises you is a question for the underlying list, not a verdict. Drill into the rows before acting on the aggregate.
• Dashboard scope follows tenant scope. Wrong-looking data usually means the wrong tenant hostname, not a broken dashboard — check the address bar first.

What next

• Tasks: the shared list behind the Tasks card.
• Deliverables: the outputs behind the Deliverables card.
• Table Views: the saved views and org defaults behind the picture.
• Menu: the navigation that leads the team here.
• Reports: deeper cuts when the glance is not enough.