Architect Academy: Using Data Cloud with Multiple Salesforce Orgs

[@sitakunz6764]

Great video on Data Cloud with Multi Org connector versus middleware but compliance what data gets accessed and which user gets the accessibility is also very important factor that needs to be considered while solutioning but again it depends on the requirements.

[@FrancisPindar]

Is there a link to the slides? Matthew is talking about things I can’t see on the slide.

[@darrellgallegos6997]

How is Seoul Sun creating their compliance with accessible/transferable data to data cloud? How is this a Platform Architect role and not a data compliance role/steward of Seooul Sun the authoritive person to discuss and allow which data points? How do you provide compliance proof data is allowed to leave one residency area to another?

[@SalesforceArchitects]

Great questions. The combined organization absolutely would need a data compliance expert to determine which data points are ok to leave a country and which ones would be required to remain resident (and provide the appropriate supporting documentation). And then from there, it would be up to an architect to ensure that all of the connectors and filters are configured properly to ensure that those requirements are met, which is what we're covering here.

[@darrellgallegos6997]

@@SalesforceArchitects that makes more sense. The way I consumed this information, just me, is that the architect would be making these calls. My point, is to ensure the business has complete and total accountability to perform this exercise, mandate, document and authorize the data transfer. Ultimately, yes Hyperforce is allowing for the seperation and isolation of data to remain in a specific geographic location; however, there needs heavily guided decisions to support transfer of data points outside the residncy location. It would be GREAT if Salesforce would establish a metadata attribute that could help inidcated data to be used in connectors. For example, some Custom Field attribute which would "block" the availability to a connector.