Definition
An Account Template is a Dashpivot template stored at the Account Layer rather than inside a specific workspace. It is editable only at the Account Layer, and can be pulled into one or more workspaces by an Account Admin.
Once an Account Template has been pulled into a workspace, it lands in the workspace's Home Folder. From there, it behaves like any other Dashpivot template — see What is the Template Library in Dashpivot? — except its structure is locked from workspace-level editing.
What it's used for
Account Templates are used to:
Maintain a single master template that needs to look and behave the same across multiple workspaces (for example, a corporate incident report, a daily site report, or a JV-wide quality form).
Push updates centrally. When the Account Admin updates an Account Template, the update flows down to every workspace that has pulled it — no need to update workspaces one by one.
Protect governance. Workspace users cannot accidentally alter the structure of an Account Template, so standard processes stay consistent across the business.
When to use it
Use an Account Template when:
The same template needs to be used in more than one Dashpivot workspace.
Consistency of fields, sections or wording matters for reporting, compliance or analytics.
You want updates to roll out everywhere automatically when the template is changed.
If a template is only used in one workspace, the existing workspace-level Template Library is still the right place to create it.
How Account Templates compare to workspace templates
Capability | Account Template | Workspace Template |
Edit location | Account Layer only | Inside the workspace |
Available in | Multiple workspaces (via pull) | One workspace |
Editable by | Account Admin | Org Controller / Project Controller |
Locked at workspace level | Yes | No |
Updates propagate | Yes — to every workspace that has it | N/A |