Hi Don, There are definitely use cases to make unomi multitenant. I'm not sure though if we should use the existing "scope" identifier or if a super scope should be added.
With the use cases that we want to address, we would scope profiles, sessions, events but we also need to find a way to scope properties, tags and any data structure change that could be done via the API... Regarding security and permissions, maybe the unomi key could be leveraged. When using multiple Unomi, are you using the same ElasticSearch cluster with different indexes ? Is this working well or did it come up with some challenges ? Romain
