Cloning across Workspaces

For assets that aren’t templates, it’s best to clone them as local assets inside of a program. With the proper access level, you can drag and drop these assets into another workspace:

  • Programs
  • Emails
  • Landing Pages
  • Forms
IMPORTANT
While all of the items listed above can be cloned across Workspaces, emails, forms, and Landing Pages must be inside a program at the time of cloning.
NOTE
When cloning assets that have templates, those templates must be shared with the destination workspace.

Moving Assets to other Workspaces

To move assets to a new workspace, put them into a folder and drag the folder over to the other workspace.

NOTE
You can’t move a program that contains members from one workspace to another.

Person Partitions

Person partitions act like separate databases. Each partition has its own people that do not de-dupe or mix with other partitions. If you feel you have a business use case that may necessitate having duplicate records with the same email address, please contact Marketo Support.

You can assign person partitions to workspaces in the following configurations:

  • one workspace to one person partition (1:1)
  • one workspace to many person partitions (1:x)
  • many workspaces to one person partition (x:1)
NOTE
Reasons you would use a person partition:
  • Your workspaces not only have different assets, but also don’t share any people
  • You want duplicates for other business reasons
CAUTION
Person partitions do not interact with each other, so be careful when setting them up.
NOTE
Previous pageEnable No-Draft for Snippets
Next pageAllow User Access to a Workspace

Marketo Engage