Skip to main content

How to create and edit an Account Template

Learn how to set up Account Templates at the Account Layer for deployment across workspaces

Written by Nina Yang

Prerequisites

Before you begin, make sure you have the following:

  • Plan: User based: Premium or high, Enterprise Unlimited: As add-on

  • Permission: Account Admin

  • Skills Required: Familiarity with the Dashpivot template editor

  • Device Type: Computer

  • Subscription: Dashpivot Web access on a Sitemate Start account

Create an Account Template

  1. Log in to Dashpivot Web as an Account Admin.

  2. Open the Account Layer from the Workspace Switcher.

  3. Click Account Templates.

  4. Click + Add Template.
    ​

  5. The Dashpivot template editor opens as a modal.

  6. Build your template — add sections, fields, formulas and any other elements as you would in a workspace template.

  7. Set the template name, description, and tags.

  8. Click Save.

The template is now stored at the Account Layer and is immediately available to be pulled into any workspace — see How to pull an Account Template into your workspace.

Edit an Account Template

  1. Click Account Templates in the Account Layer navigation..

  2. Click the Account Template you want to edit. The Dashpivot template editor opens as a modal with the template loaded.

  3. Make your changes — add, move, rename or remove fields and sections; update formulas; update the name, description or tags.

  4. Click Save.

When you save, the backend automatically syncs the updated template to every workspace that has pulled it. No additional pull action is required.

Key differences from workspace templates

The template editor at the Account Layer is the same editor as found in Dashpivot — but a few elements behave differently as the template doesn't belong to a specific workspace until it's pulled in. These differences apply to both creating new templates and editing existing ones.

Lists referenced inside the template

When you add a list field, the list picker shows Account Lists rather than workspace lists.

  • Only lists that exist at the Account Layer are selectable in an Account Template.

  • After the template is pulled into a workspace, the workspace will automatically receive the referenced Account List as part of the pull (if it isn't already there).

Logo placeholder

Templates can include a logo. In the Account Layer editor:

  • The logo field shows a placeholder image.

  • When the template is pulled into a workspace, that workspace's logo is automatically applied at deployment.

  • You do not need to upload a logo at the Account Layer.

Counter / folder path preview

If your template includes a counter or folder-path reference, the preview shows a static [Folder path] placeholder rather than an actual folder.

  • The folder path is resolved when the template is deployed inside a workspace.

  • You do not need to configure a folder path at the Account Layer.

What happens to existing forms when you edit a template

When an Account Template is updated and saved:

  • Existing forms keep their original structure. Forms created before the update retain the fields, sections, and formulas they were created with. They will not change.

  • New forms use the latest template. Any form created after the update will reflect the new template structure.

  • Workspace users see the new template version. The Template Library in each workspace updates to show the latest version, but historical forms are not retrospectively modified.

Notes / Tips

  • The editor is the way to create and edit Account Templates. There is no import option — every Account Template is built using the editor at the Account Layer.

  • Account Lists must exist first. If your template uses lists, create those as Account Lists before you build the template — as Account Templates can only reference Account Lists.

  • You don't need to set a logo or folder path at the Account Layer. Both are resolved at deployment using the target workspace's settings.

  • Save propagates updates automatically. Once a template has been pulled into workspaces, any save at the Account Layer pushes the new version everywhere it lives.

  • Lock behaviour is unchanged by edits. The template stays locked at the workspace layer before and after an edit. Workspace users cannot opt out of an update.

  • Account Lists referenced inside the template are unaffected by template edits. They update independently — see How to create and edit an Account List.

  • Archive a retired template rather than deleting it. Deletion at the Account Layer also removes the template from every workspace that has pulled it; archiving keeps it for future reference.

Troubleshooting

Problem

What to check

List picker is empty when adding a list field

The list must exist at the Account Layer first. Create it as an Account List, then return to the template editor.

Logo placeholder is showing in the editor preview

This is expected — the workspace's own logo will be applied when the template is deployed in a workspace.

Counter shows [Folder path]

This is expected — the folder path is resolved when the template is deployed inside a workspace.

Save was successful but workspaces don't see the change

Ask a workspace user to refresh Dashpivot. The sync should complete shortly after save.

A field I removed still appears in old forms

This is expected — existing forms keep their original structure. Only new forms reflect the update.

Related Articles
Did this answer your question?