Lesson 4 of 10 · 3 min

The Projects List: Layout and Entry Points

Understand the Projects page structure available to provider roles — the heading, view modes, pagination, and how the page adapts per role.

The Projects List: Layout and Entry Points

Video coming soon

4/10

Lesson Notes

01

Provider roles (Owner, Admin, Project Manager, Technician, Editor) land on a page titled 'Projects' at /jobs. This is distinct from the agent's 'My Orders' view — same URL, different component tree. Owners, Admins, and Project Managers see all projects in the organization via the /projects endpoint. Technicians see only projects where they are assigned as the technician, and Editors see only projects where they are the assigned editor — this scoping is enforced server-side through the /projects/mine endpoint, not by frontend filtering. The component that renders for all manager-level roles is JobsView with activeView='all'.

02

The Projects page defaults to list/grid view with server-side pagination. The default sort is by scheduled time descending (most recent first), displaying 12 jobs per page. Controls in the toolbar let you change the sort field (scheduled time, client name, priority) and sort direction. A page-size selector offers 12, 24, or 48 items per page. Pagination controls appear at the bottom of the list when the total count exceeds the page size. All of these choices — status filter, page, page size, sort field, sort direction, and all advanced filters — are synced to URL query parameters so the exact view can be bookmarked or shared.

03

The view can be switched between grid (card layout) and table (row layout) using a toggle in the toolbar. The table view adds columns for Property, Client, Scheduled, Package/Media Types, Priority, Status, and Technician, with inline status dropdowns on each row. The grid view shows JobCard components — each card displays the property address, scheduled date, status badge, priority badge, client name, assigned technician avatar, and media type icons.

04

For managers, there is an additional Saved Views button (the bookmark/views icon) next to the filter controls. Saved Views let you name and store any combination of filters — status, sort, technician, editor, PM, customer, package, media types, and date ranges — so you can recall a complex filter with one click. On iOS, the DispatchView provides the equivalent surface: a list/map toggle, time-based filter chips (All, Today, Upcoming, Past, In-Flight), and swipe actions on each row.

05

The Job Management page at /job-management is a separate route that shows the Kanban board view (activeView='kanban'). It is designed for Owners, Admins, Project Managers, Technicians, and Editors who prefer a visual pipeline view over the paginated list. The Kanban board and its columns are covered in the jobs-status lesson.

Key Takeaways

  • Managers see all org projects via /projects; Technicians and Editors see only their assigned jobs via /projects/mine — scoped server-side.
  • Sort, filter, page, and page-size are all URL-synced so the current view can be bookmarked or shared.
  • Toggle between grid (JobCards) and table (row + inline status dropdown) using the view mode control.
  • Saved Views let managers store named filter presets for one-click recall.
  • The Kanban pipeline lives at /job-management; the paginated list lives at /jobs — both serve provider roles.
Related documentation at docs.vremly.com