Skip to main content

Per-project dashboards

A per-project dashboard lives on a single project rather than across the whole organisation. Widgets on a project dashboard auto-narrow their data to that project; you cannot accidentally surface other projects' work orders or submissions on it.

Per-project dashboards pair naturally with project sharing and client portals: a customer can give a contractor a focused board for their project, or render a client portal with a project-scoped dashboard so the customer's end-stakeholder sees only the project they care about.

For general dashboards that span the whole organisation, see Dashboards.

Create a project dashboard​

  1. Open the project.
  2. Click the Dashboards tab.
  3. Click + New dashboard.
  4. Enter a Name and Slug.
  5. Click Create.

The dashboard opens in the editor with an empty grid. It is automatically scoped to this project.

Clone an org-level dashboard onto the project​

If you have a working org-level dashboard you want to copy onto a project:

  1. Open the project's Dashboards tab.
  2. Click + New dashboard → Clone from org.
  3. Pick the source dashboard.
  4. Pick the new name and slug.
  5. Click Create.

The clone is project-scoped from creation. Widgets are duplicated but rebind to project-narrowed data.

How narrowing works​

When you add a widget to a project dashboard, the widget's data source is automatically narrowed to the project. The following kinds narrow correctly:

  • Submission widgets count or group submissions where the form was captured against a work order on this project.
  • Work order widgets count or group work orders on this project.
  • Chainage widgets narrow features to routes belonging to this project.

The following kinds are not supported on project dashboards in V1:

  • Feature widgets (counts of geographic features in a feature class). Feature classes are organisation-scoped, not project-scoped, so a "count of features" on a project dashboard would be ambiguous. Use a feature widget on an org-level dashboard instead, or split the underlying feature class.

Attempting to add a feature widget to a project dashboard returns a clear error message pointing at the org-dashboard alternative.

Share access to a project dashboard​

A project dashboard inherits access from the project's share rules:

  • The owning organisation has full access.
  • CONTRACTOR shares can read and write the dashboard.
  • VIEWER shares can read only.

Non-share callers cannot see the dashboard's existence at all (a 404, not a 403, so the dashboard's slug cannot be enumerated).

Render a project dashboard in a client portal​

  1. Create the project dashboard as above.
  2. Open Client portals on the project.
  3. Mint a new portal and enable Dashboard mode.
  4. Pick the project dashboard from the multi-select.
  5. Save and share the portal URL.

The recipient sees the dashboard rendered with live data, narrowed to the project, with no Stratumly login required.

What next?​

  • Project sharing: the access primitive that gates who sees the dashboard.
  • Client portal: expose the dashboard to someone without a Stratumly account.
  • Dashboards: the org-level dashboard surface.