Skip to main content

Import & Export

You can export any template from Click as a file, then import it into another environment or organization. This is useful for promoting a finalized template from staging to production, keeping a backup, or starting a new template from an existing one.

Exporting a Template​

  1. Go to Click → Templates.
  2. Find the template you want to export.
  3. Click the ⋯ menu → Export.
  4. The template configuration downloads as a .json file.
Coming Soon

Screenshot: Template row with the ⋯ menu open, showing Export highlighted

What the export includes:

IncludedNot included
Template type and nameAcceptance records
Agreement contentEvidence bundles
Acknowledgment settingsDeployment configurations
Appearance settingsSession history
Variable definitions (Generated templates)
Category definitions (Consent templates)

Importing a Template​

  1. Go to Click → Templates → Import Template.
  2. Upload the .json file.
  3. Review the summary — template name, type, and the number of variables or categories detected.
  4. Click Confirm Import.
Coming Soon

Screenshot: Import Template dialog showing the summary with template name, type, and variable count

The imported template is created as a new Draft, independent of the original. You need to review it and publish it before it can be deployed.

Cloning a Template​

Cloning creates a copy within the same organization — useful for creating a variation of an existing template or starting a new version under a different name.

  1. Go to Click → Templates.
  2. Click ⋯ → Clone.
  3. Enter a name for the clone.
  4. The clone is created as a Draft with all the same content, settings, and variables.
Coming Soon

Screenshot: Clone Template dialog with the name field and a Create Clone button

Copying a Template from Staging to Production​

A common workflow for teams that test agreements before going live:

  1. Finalize the template in your staging organization.
  2. Export the template configuration.
  3. Import it into your production organization.
  4. Review the content and settings in the new draft.
  5. Publish it.
  6. Create a new deployment pointing to the production domain.
tip

Save the exported JSON file to your version control repository. This gives you a history of template changes and makes it straightforward to roll back to a previous version if needed.

Exporting via API​

For developers who want to automate template backups or manage templates programmatically, templates can also be exported via the Click API. The response is the same JSON format as the dashboard export.

See the Click API reference for details.

Next Steps​