Hello,
I'm in the process of setting up Workspaces and Partitions for our instance and I have some questions that I can't seem to find any documentation on. We have two brands (so I'm setting up two partitions and/or two workspaces) that don't share leads, so we can have duplicate leads across brands, however, we will not be duplicating contacts or accounts - which I understand will lead to difficulties, but short of revamping the SFDC setup, I imagine I'll have to solve for this on my end.
Maybe those questions aren't even the right ones, but any help in guiding me during this setup would be greatly appreciated!
Thanks
Solved! Go to Solution.
Hi Steven,
You do not necessarily have to set a 1 to 1 relationship between partitions and workspaces. Assets (smart campaigns especially) are controlled by workspaces and will operate on any person they can access from the workspace they belong to. A partition can be accessed from multiple workspaces.
You should create a few additional workspaces in addition to (and not in lieu of) the 2 workspaces you are planning:
With this structure, you will have more possibilities to implement what you need.
-Greg
Hi Steven,
You do not necessarily have to set a 1 to 1 relationship between partitions and workspaces. Assets (smart campaigns especially) are controlled by workspaces and will operate on any person they can access from the workspace they belong to. A partition can be accessed from multiple workspaces.
You should create a few additional workspaces in addition to (and not in lieu of) the 2 workspaces you are planning:
With this structure, you will have more possibilities to implement what you need.
-Greg
Thanks, Grégoire Michel!
A couple quick follow up questions:
Thanks again
Hi Steven,
I have a master Sandbox account where I'm building all of this out first. My plan was to provide access to users so they could test stuff here. Besides the overhead of maintaining the sandbox, do you foresee any shortcomings with this approach?
No, that's perfect, I recommend that you ask support to enable UID on both your instances, so that users can switch from one to the other without having to disconnect/reconnect. I find that paying for a sandbox just for this is not necessary, as a separate WS does the job. Also, it's much easier to share elements (e.g. templates) with a WS than between 2 instances.
Is the intention of this WS to be the holder for all templates?
LP templates, email templates and also program templates, yes.
The interest is that you can control who can access this WS and it has no data in it, which makes template testing safer.
-Greg
Question for you since you are an Expert in this area .
Do you see any negatives to making workspaces based on technologies? When we first set up our instance, we did partitions and workspaces by geography. We want to keep partitions as-is, but we are seeing a need to change our workspaces around a bit so that certain technology groups only have access to their workspace. Let me know your thoughts.
Hello Steven Musche , I am just curious if you got your situation solved? I am asking because I am in the middle of a marketo implementation and we also have two brands in two separate markets, so this is very relevant!
Also did you use the help of a marketo consultant or you built it all yourself? So I know what's the cost involved with partion/workspace.