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,

[raprohaska]

This isn't necessarily a real scenario for us. I made up the example to ensure clarity of the question, which is, when Type (on Domain record) is set to MSP, is there any functional gain? Restated, is there code anywhere (OOB) that says "user.sys_domain.type == 'MSP'" then do something special.

[jberk]

In my experience you just would put the company field on the cmdb form as a mandatory field and whenever a new CI is created the company field would set the domain. MSP users would have a contains/visibility relationship as well as sit above all the domains they manage and thus the MSP users should have access to update all data and report on any data they need while the domain/company defines ownership. You wouldn't need to do anything special if you granted the client access to the instance because they would be scoped to only their domain and thus only see CI's that fall in their own domain. To those users it would seem as if they were the only client using the instance.

[raprohaska]

That can be totally true depending on the need and I think that is pretty much what I meant in my "simplistic domain structure" example.

In my case, our clients use us for two sets of services. They may use us for ServiceNow services and they control all their own infrastructure and completely own the work. But we also have leveraged services where we own the hardware, the data centers, etc. The client may even call into our ServiceDesk but be treated as if it is their own.

Because of this, we have scenarios which data crosses domain boundaries. We are moving to a more business service based model where the clients work against services defined in their client domains but there will still be situations that once my company picks up a client ticket, it will need to refer to CIs (and possible other data) in our own domain. We can do this with Toggle Domain Scope, and as I learned about yesterday, we can change the "glide.sys.domain.use_record_domain_for_data" system property so that data for the MSP users is directly available from client domain records.

But this is way off topic for this particular thread. The bottom line to the original question is that setting Type = MSP does not have any affect on the application. It is simply a way to categorize the domains. "Contains" and "Visibility" domain features are what grant access and affect usability of the system from a domain perspective.