Skip to main content

How to Delete a Template on Dashpivot Web

Learn how to delete a template to permanently remove it from your Dashpivot workspace

Written by Adriana De Souza

Deleting a template in Dashpivot Web fully removes that template from your workspace, including all associated forms and any analytics linked to it. This action is irreversible, so it’s generally recommended to archive templates instead, keeping them out of your active library while preserving past records and data. The steps below show how to delete a template via the Dashpivot Web interface.

Prerequisites

Before you begin make sure you have the following:

  • Plan: Any Dashpivot Plan

  • Permission:

    • Home Folder Templates - Org Controller ( or higher)

    • Team Folder Templates - Team Controller, Project Controller, Org Controller

  • Skills Required: Dashpivot

  • Device Type: Computer

  • Subscription: Dashpivot Web

Step-by-Step Instructions

  1. Go to the Home Folder, then click Template Library.

  2. Select the checkboxes next to the template(s) you wish to delete.

  3. Click Archive to move the selected template(s) out of your active library.

  4. Switch to the Archived tab.

  5. Again select the checkboxes next to the template(s) you wish to delete.

  6. Click Delete to permanently remove the template(s).

  7. In the delete confirmation modal, review the full linked-template chain shown as an indented tree view with red badges. This gives you a complete view of all templates that will be permanently deleted before you confirm.

Notes / Tips:

  1. Deleting a template is a permanent action once done, the template and its associated data cannot be restored by the user.

  2. Consider archiving templates instead of deleting them if you might need the data later.

  3. The delete confirmation modal shows the complete linked-template chain — including grandchildren and all deeper linked templates — as an indented tree view with red badges. This is a preview only so you can see exactly which templates will be affected before you confirm. The actual delete and undeploy behaviour is unchanged.

Did this answer your question?