Share
ReportParent company is starting up three small start-up companies (A, B, and C). Parent company owns each of these companies, but they have separate legal names/appear distinct from the parent company. At the beginning, several of the same individuals will work in each of the start-up companies' A, B, and C CRMs, but eventually as they take off employees will only work for one company/instance of CRM. Initially I suggested that A, B, and C each have their completely own separate Dynamics CRM Online instances, and that users would need to log out and log in when they need to switch between companies.
I've seen the suggestion where some people say to just create separate departments/units in one CRM instance, which I could understand if it was the same company just different departments but I don't think it would make sense for the scenario above. Yes the first scenario would have additional licensing costs such as John Doe needing a CRM license for company A, another license for B, etc but wouldn't this simplify management, customization, and performance a lot? Management is hesitant to separate the companies and wants a holistic view of the data which I can understand, but I'm trying to think of how complicated securing the data could get between the companies as well as thinking long term.
Thoughts?
Dynamics Online
Posts I've looked at so far:
*This post is locked for comments
All responses (
Answers (
292,516
