Sharing program templates across workspaces

[Allison_Munson]

My team is beginning to use multiple workspaces across regions, and I want to set them up with access to all of our program templates I've built (for webinars, quote request campaigns, etc.)

You can't directly move a program across workspaces, but various posts on here say you should be able to move folders between workspaces, and that those folders can have programs inside them. I have not been able to accomplish this, unfortunately. Whenever I try, I get error messages that assets in the folder are in use and can't be moved. All of the assets and campaigns in the program I'm trying move, though, only reference other assets/campaigns in that same program. I've tried unapproving assets and making sure all campaigns are off, but I still get this issue.

Any suggestions?

[Michael_Florin]

The usual suspects are Snippets and Templates. Be sure that they are shared with all workspaces you are cloning into.

[uditmathur]

Hi Allison Munson

Yes, you cannot share Programs directly across workspaces, they must be inside a folder. The word of caution here is Only parent folder containing your assets can be shared not the child folders.

You should be able to share Email templates, LP templates, Models, Smart campaigns, smart lists, Segmentations, Snippets across workspaces.

You can get the step by step guide for sharing across workspace from here.

Hope this helps.

[Michael_Florin · Accepted solution]

Please allow some remarks on wording and the concept of a "Program Template".

A Program Template is a program that contains various emails, landing pages, Smart Campaigns and tokens, and this program is supposed to be cloned and then to be adapted for the specific use case.

You don't want to share it - because you can't share programs - but you also don't want to move it, as it's supposed to stay where it is in its central place/workspace. You want to clone it. But cloning a program across workspace borders is tricky, as all dependencies of the parent program need to exist in the target workspace. And these dependencies usually are: Email Templates, Landing Page Templates, Snippets or Segmentations (Marketo is not super-explicit in telling you what exactly is missing in the target workspace when it rejects your cloning process). So all of these dependencies need to be shared across workspaces.