Skip to main content

How to Clone a Team Folder on Dashpivot Web

Learn how to clone a team folder in Dashpivot to quickly replicate an existing folder's setup for a new site, crew, or job.

Written by Nina Yang

Cloning a team folder creates a new folder with the same templates and setup as an existing one — without copying any forms or records. This is useful when a new site, crew, or job needs the same structure as one you already run.


Prerequisites

Before you begin, make sure you have the following:

  • Permissions: Org Controller or Project Controller

  • Device: Computer or tablet

  • Subscription: Dashpivot


Step-by-Step Instructions

Clone a Team Folder

  1. Open the folder list and locate the team folder you want to clone.

  2. Click the three-dot menu next to the folder.

  3. Select Clone Folder.

  4. Review what will be copied in the confirmation modal.

  5. Click Confirm.

The cloned folder is created in the same project as the original and named Copy of [folder name]. If a copy already exists, the next one is numbered (Copy(1) of…). You can rename it afterwards.


Who Can Clone a Team Folder?

Role

Can Clone?

Org Controller

✅ Can clone any team folder in the workspace

Project Controller

✅ Can clone team folders in projects you control

Team Controller

❌ Cannot clone folders

Member

❌ Cannot clone folders


What Gets Cloned?

Cloning copies the folder's setup — not its data.

What comes across

  • The team folder itself, created in the same project as the original

  • Templates created in the folder

  • Templates deployed to the folder from the workspace level (re-deployed, so they stay linked to the workspace template and continue receiving updates)

  • Template tabs

  • Photo tags on the team folder

What does not come across

  • Forms and records — cloning copies the folder setup, never the data inside it

  • Users and their permissions — you will need to add people to the new folder yourself

  • Lists — lists sit at the project level and are not part of a team folder clone

  • Archived templates — anything archived or deleted in the source folder is skipped


Requirements & Limitations

  • Team folders only. Cloning project folders is coming in a later release.

  • Same workspace only. You cannot clone a folder into a different workspace.

  • Active folders only. Clone Folder is not available from the Archived view.

  • All or nothing. If something goes wrong partway through, nothing is created — you will get a single error message and no half-built folder is left behind. You can safely try again.


Platforms

  • Available on web

  • Not available on the mobile app


Frequently Asked Questions

Why can't I see the Clone Folder option?

The Clone Folder option only appears when all of the following are true:

  1. You are an Org Controller or Project Controller (see the table above)

  2. You are looking at a team folder, not a project folder

  3. You are in the active folder view, not the Archived view

If you meet all three and still cannot see it, contact your Org Controller or Sitemate support to check whether the feature is enabled for your workspace.

How can I track when folders were cloned?
A clone is recorded as a single entry in the activity feed, showing who cloned the folder, when, and how many items were copied across with it. You will not see a separate line for every template.

Will my forms and records be copied into the new folder?
No. Cloning copies the folder's setup — templates, template tabs, and photo tags — and nothing else. The new folder starts empty.

Do I need to re-add users to the cloned folder?
Yes. User access is not copied, so you will need to add people to the new folder yourself.

What happens to templates deployed from the workspace level?
They are re-deployed into the new folder rather than copied, so they stay linked to the workspace template and keep receiving updates.

Did this answer your question?