MSP supporting other MSP providers

[Lowell Coleman]

Hello,

We're an MSP and have a domain separated instance and had questions around supporting other MSP providers in our instance. We're looking for best practices around loading foundation data (location, contacts) for our client's (MSP) clients.

Should we add our client's ABC Company (MSP) clients contacts under ABC Company and differentiate them by Department or Location?

Should we build our client's clients under their own 'Account/Company'?

We could run into an issue where we sell services to our client's clients and they become our client. So if we build these contacts under our client (MSP) then they wouldn't be able to exist under a 2nd Accounts/Companies (their company).

[kdwessel]

You may have business requirements to support both in your instance like we do. If you add them as contacts in an existing company and differentiate by Department or Location, consider that on forms like Service Catalogs you would need to be careful in displaying the Location and/or Department field so they do not see all the values (different company names). Also, if you allow them to submit a Case or Incident or Service Catalog item on behalf of another person and they need access to the user table to search/select a user, they would see the other users unless you restrict in some way so they only see those users of their specific Location or Department. Alternatively, you can limit it so they can only submit a Case or Incident or Service Request for themself. If there are integrations/eBondings, that is a 'lever' that justifies their own company in our MSP to ensure data and transactions are not unintentionally sent to the wrong client.