5 Replies Latest reply on Sep 28, 2017 2:04 AM by DLodge

    Benefit of seperate tenants within ISM




      I'm trying to understand the benefits and any draw backs of having seperate tenents within ISM? As I understand it, any additional instances (UAT, Staging, Dev) utilise the core infrascture deployed by Service Manager however each instances saves it's configuration into seperate databases within the SQL Cluster. The additional isntances all still reside within the production Active Directory domain and would be subject to change control as they.


      What are the primary use cases that I'm missing for using seperate tenants?


      I'm struggling to understand the benefits of using tenants instead of creating additional objects in Service Manager and then once they've been tested and approved, pushing them live and removing the devleopment objects.


      Am I missing something? Any information would be very welcome,

      Many thanks