How to request a dashboard customisation (add column, filter, KPI)

Jules dashboards are configured per-customer. If a column, filter or KPI is missing or behaves differently than you expect, you can request a customisation through the support team. This article explains the information to provide to keep the back-and-forth short.


What can be customised


  • Columns in the main data table (e.g. add Address, City, Site).
  • Filters at the top of the dashboard (date type, status, etc.).
  • KPI tiles above the table (counts, sums, averages).
  • Charts (bar, line) — fields and grouping.
  • Row navigation — which page opens when a row is clicked.


What to send to support


Send to help@julesai.com or chat in Jules:


  1. Dashboard URL — copy the URL from your browser, e.g. https://app.haroldwaste.com/dashboard/11.
  2. What to change — add / remove / rename / fix.
  3. For new columns — column name and which field it should pull from (e.g. "Site → Address 2 of the site linked to the load").
  4. For filters — what date or attribute should it apply on (e.g. "filter by contract date" vs "filter by shipment date").
  5. Screenshot — annotated if possible.


Typical questions support will ask back


To avoid round-trips, anticipate these:


  • Which date should the top-level date filter apply to? (contract / shipment / created date).
  • Should the dashboard include all loads, or only loads linked to an open purchase or sale?
  • For aggregated rows (multi-material containers), do you want one row per load × material or one row per load?
  • On row click, where should the user land? (purchase contract, sale, shipment, …).
  • Should KPI tiles and charts stay, be removed, or be redesigned?


Turnaround


Most column / filter additions are completed in 1–3 working days. Larger redesigns (new chart types, restructured tables) may require a product review.


Technical context


Dashboards in Jules are stored as configurable widgets (table, KPI, chart) pointing at GraphQL queries. The data is built from the Jules database (operations, contracts, loads, shipments, invoices), so any field stored in the system can usually be surfaced — even if it is not yet in the dashboard. Custom calculations (e.g. KPI based on a formula) may require a small dev change.

Updated on: 11/05/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!