Domain Separation, Type = MSP

[raprohaska]

I think I understand but want to make sure. When using domain separation, each domain is given a "Type" choice (OOB) of MSP, Customer, Vendor. From what I can tell the type of domain is simply for categorization and does not bring any functionality along with it. Visibility is dictated by contains and visibility domain while access to functionality such as domain picker, toggle domain scope, etc. are controlled by role.

Is there any functionality that I'm missing from a domain type = MSP perspective within domain separation?

Thanks,

[Michael Fry1]

While you are correct that it is for categorization, type = MSP says this domain contains Overrides, and probably the Default domain is sub-domain and this MSP domain uses Contains to connect to another domain like TOP and so on. It helps bring structure to the whole domain list and of course, you can have more than 1 MSP domain.

[raprohaska]

Let's say we have have the following domain structure. In this structure we have the obvious data segregation. Parent 1 can see their own data plus data in Middle. Parent 2 can see their own data plus data in Middle. Parent 1 and Parent 2 cannot see each other's data. Apart from that, the only difference is the domain type. Parent 1 is a Customer domain, and Parent 2 is a MSP domain. Beyond data access, how does the user experience different for users within Parent 1 from Parent 2, simply based on type?

[Michael Fry1]

It should not differ at all. I would say, you should not have Parent 2 as MSP in this case, but TOP would be your MSP and contain your global overrides. P1 & P2 are just Customer domains with access to another domain.

[jberk]

TOP would contain your global overrides but would you put the employees of the MSP in the TOP domain?