See what is yours to do, the moment you log in

What this module does

A new user logs into Visual Tracking on day one expecting to spend an hour finding what is theirs in a sprawling product. With the personal dashboard, the new user sees in 10 seconds: this is what I owe today, this is what is in my work centres, this is what is overdue. No setup, no view configuration, no inherited filter from a colleague's session. By the end of the first week, the dashboard is a habit, and the rest of the product is a place the user navigates to from a context they already understand.

Key pages

General is your home screen, and it sets the controls the rest of the product reuses. The Dashboard is scoped to you with no configuration: My Tasks shows the tasks the user owns; My Queue shows the operations in the work centres the user manages. Counts call out overdue, due today, and this week, and a “next up” list points at where to look first. Underneath every module is one shared data table with global search, stackable filters shown as chips, click-to-sort columns, density control, and CSV export. The full filter and sort state lives in the URL, so a filtered view is a link a colleague can open. Identifier badges on projects, items, orders, and operations open the messages, documents, and NCR in place, and flag a non-conformance in red.

Operators stop guessing what to start next. Project Managers do not maintain a private list of “things I am tracking” beside the actual product, because the dashboard already shows it. A planner sends a filtered queue view as a link instead of “open the page, set these five filters, see what I see.” And the new user who joined on Monday has a working home screen on Monday afternoon, not after a four-week onboarding to understand which view is theirs.