Preparations for Multi-Tenancy in Camunda 8 SaaS

Hello everyone,

We are currently setting up a cluster for our customer and we aim to switch over to a multi-tenancy setup as soon as it is available, to separate our business units logically without setting up several clusters.

Until then: Is it possible to already prepare things regarding deployments, connectors, workers etc. that we can do? I’d like to be ready for a migration for multi-tenancy and reduce the efforts later. For example, are there any best practices: can we already set a tenantId during deployment or will it always be overwritten by the default identifier on SaaS.

Thanks in advance
Stefan

Hello @itsmestefanjay ,

in my experience, the easiest way to set up a Camunda 8 instance that should use multi-tenancy at some point is by setting it up with multi-tenancy upfront.

Then, you can use the <default> tenant in the first place and introduce more as required.

Best regards,
Jonathan