Question/advice about Marketo Workspaces! This is the currently how our business/team is structured:
|B2C Customers (Free)||Expansion Retention|
|B2C Customers (Biz/Pro)||Expansion Retention, Events|
|B2B Customers (Enterprise)||Expansion Retention, Events|
|B2B Prospects||Acquisition, Events|
|B2C Prospects||Acquisition, Events|
We are proposing to create multiple workspaces using a single lead partition. Any feedback you recommend to go down the workspace route or maybe not.
My recommendation would be not to use workspaces at all. The disadvantages outweigh the advantages.
The main reason to have workspaces is user access control. (Structure can also be achieved through folders and naming). And in my tenure in Marketing Automation - 8 years with two Marketo deployments - I have never experienced any user overstepping their boundaries and reaping havoc in an area they are not supposed to be in. You have hired them, you have trained them, so you better trust them. 🙂
And the disadvantages are all features that don't work across workspaces: Requesting campaigns, inheriting global folder tokens, restrictions in the cloning process, referencing lists or programs across workspaces...
My former Marketo had workspaces, and the experience with that situation led us to not have workspaces anymore in our current Marketo. ~30 users, supporting ~20 different products in all phases of the life cycle in 6 languages, and we're doing good. Happy to have made that decision.
Thanks so much for the feedback! Yes that is very true that campaign owners shouldn't mess around within Marketo. Also good to know the restrictions/constrains of having a workspace...seems more of a pain in the butt and not scalable.
Our Marketo instance has multiple workspaces without lead partitions for the below reasons:
1. Limited access to users for certain brands/products they are responsible for
2. We do have routing rules set up in each workspace and wanted to enforce accountability for their rules
3. We have a default workspace where we build all our Data Management/subscription center rules etc. Anything related to system level changes or data updations happen here which is accessed by Admin and core team.
So far we are fine with this set up given few challenges that Michael stated and the major one ofcourse is cloning.
Another recommendation is to host all master templates/assets in a Default workspace which is shared across workspaces.
You don't need routing rules without partitions. There's only one partition/database that's shared by all workspaces, so nothing to route.
We have built routing rules in Marketo instead of SFDC to route our online and offline leads that enter Marketo. There will be no dependencies as it is a single partition. Anything that enters marketo is pushed into respective routing rules built in the workspaces based on the parameters associated with that record and gets routed to the right queue or person in CRM.