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.

Organization dashboard templates in the Templates gallery
Predefined chip while it stays synced to the source. Customize it and that site leaves the sync track.

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.

