# Duplicate a proven experience setup into another workspace?

Asked by Freya Dahlberg on 2026-05-13. Tags: workflow, workspaces, templates, cli.

We run several brands, each in its own workspace. For brand A we have a
returning-visitor experience that took real iteration to get right: the
component, the slot, the audience condition, all of it. Now I want to replicate
that exact setup in brand B's workspace without rebuilding every piece by hand
and hoping I remember all the details.

Is there a supported way to package and reapply an experience setup across
workspaces? Copy-paste between workspaces does not seem to exist, which I
assume is deliberate given they hold separate data

## 1 answer

### Accepted answer from julius_h (2026-05-13)

Templates are the supported path, and they live in the CLI:

```croct-cmd
croct create template
```

packages a setup, and

```croct-cmd
croct use <template>
```

applies a template to whatever workspace you are working against. So the
workflow for your case is: create a template from the brand A setup, then run
`croct use` in the brand B project. That gives you a reproducible artifact
instead of a manual rebuild, which is exactly what you want when
standardizing playbooks across brands.

This is the same mechanism behind Croct's own template gallery, for example
the [Sanity personalization template](https://croct.com/templates/integration/cms/sanity-personalization),
so it is a first-class workflow, not a workaround.

And your assumption is right: workspaces are isolated by design, each with its
own applications, environments, and audiences. Cross-workspace reuse goes
through templates or re-creation, never live sharing, so brand data stays
cleanly separated.

#### Reply from Freya Dahlberg (2026-05-14)

Tested it this morning: templated the brand A setup and applied it to brand
B in a few minutes. Adding "create template" to our playbook checklist so
every proven setup gets packaged going forward. Thank you.