Skip to main content
Both copy a dashboard from one place to another, but they answer different needs. Templating gives you a starting point you expect to modify. Deployment gives you parity; the copies stay governed and in sync.
Choose by asking whether the sites should stay identical after the copy is made.

Independent copy vs live sync

The deciding question is the relationship after the copy is made:
  • Templating produces an independent copy. You template a chart, page, dashboard, or whole collection, then use that template wherever you need a head start. Edit freely — there is no ongoing link to the original. See Template types.
  • Deployment produces a governed copy. The Deployment Manager pushes one dashboard to many buildings and keeps them synced: publish a new version at the source and every predefined copy updates. See Deployment manager.
A template is a photocopy you are free to mark up. A deployment is a live mirror that keeps reflecting the source. Organization templates live in the Templates gallery as independent starters you apply and then edit.
Templates page with Dashboards filter selected showing Organization Templates cards such as Comfort and Air Quality, Lighting, Operations, and Site Summary

Organization dashboard templates in the Templates gallery

A deployed dashboard shows a Predefined chip while it stays synced to the source. Customize it and that site leaves the sync track.
Overrides dashboard showing a Predefined status chip, Customize Dashboard and Edit Dashboard buttons, KPI cards, charts, and an overridden points table

Predefined deployed dashboard with Customize Dashboard available

Template or deploy

These are not mutually exclusive. A common pattern is to template a variant for sites that genuinely differ, and deploy the standard version everywhere else — escaping parity deliberately rather than accumulating ad-hoc custom views. Templates can also be exported and imported across organizations (24-hour secure URL) and exist at organization or global scope. They can carry Building Data Hub pipeline dependencies so the data plumbing recreates with the layout. See Template types.
  • Templating is independent, so no copy benefits from later improvements to the original.
  • Deployment maintains parity, so a flaw published once reaches every linked site. Test before deploying.
  • Do not use templating to solve a visibility problem. Making a dashboard visible to roles is what collections are for.

Next steps

Templates

Create and apply templates.

Deployment manager

Deploy dashboards and keep sites in sync.
Last modified on August 18, 2026