How the Dashboard Works for Your Role

The Vremly dashboard is not a single screen — it is three distinct views wired to your identity. When you sign in, the system resolves your account type (AGENT, PROVIDER/COMPANY technician, or company dispatcher) and your workspace type (personal org vs. company org), then routes you to the dashboard layout that matches. This means two people opening the same /dashboard URL on the same org can see completely different things based on their roles.

Agents — real estate professionals who commission shoots — see the Agent Dashboard: a full-screen address search bar at centre, today's scheduled orders below the fold, and (when enrolled) a loyalty rewards widget. The goal is a single tap to book or check on an order. On the iOS app, this maps to AgentDashboardView, which opens with a large greeting heading, a capsule-shaped quick-book search bar, and three quick-action pills: All orders, Calendar, and New order.

Independent providers and company-level technicians or editors see the Provider Dashboard: four stat cards at the top (Upcoming Jobs, Total Completed, Rating, On-Time Rate), followed by a compact month-view schedule, a Live Job Map, and an Active Jobs grid. Editors see only the jobs assigned to them as editor; technicians see only their own assigned shoots. On iOS, providers in a personal workspace land on ProviderPersonalDashboardView, which leads with 'Jobs today' and 'First stop' metric tiles plus a prominent Start trip card that launches turn-by-turn navigation.

Company owners, admins, and dispatchers see the Company Dashboard: a timeframe picker controlling six org-level metric cards, a compact month calendar fed from the full booking schedule, a Live Project Map with provider pins and pending assignments, and an Active Projects grid showing the four most-recently-assigned jobs. This is the command-centre view for running operations across the team.

Switching workspaces — via the workspace picker in the top bar — always reloads the dashboard for that org. On iOS, a workspace switch triggers a new bootstrap fetch keyed on bootstrapEpoch, re-populating every counter and the map with data scoped to the selected org. You never need to manually refresh after switching.