Do Elsa v3 support multitenancy?

[abhjitsantra]

I am dealing with a business problem where multiple tenants can use the same set of workflows, but the workflows need to be made available to a tenant based on some feature flag. The workflow instances should be segregated by the tenants. Can we achieve this in ELSA v3?

[sfmskywalker]

Hello @abhjitsantra

Elsa 3 has no multi-tenancy support at this moment, but I am planning on working on it fairly soon, ideally before the 3.0 release later this year 🤞🏻

Thanks by the way for pointing out the requirement of having multiple tenants have access to the same set if workflows, I had not considered that use case 🤔

[sfmskywalker]

I'm loving the excitement! I am working on documentation to setup multitenancy, but if you want you can already checkout the Elsa.Server.Web project in this repo. You'll notice there's a variable called useMultitenancy that you can set to true. Follow its usages throughout the Program.cs file to get an idea of how to setup multitenancy in your own app.

[hpposch]

Alright, thank you.
I will check that out.
Is it only working for Elsa-Core or ist also implemented in Elsa-Studio?

[sfmskywalker]

Elsa Studio is automatically "scoped" to the tenant associated with the signed-in user. Perhaps in a future update we'll add some tenant management UI that would then also allow you to switch between tenants.

[EngSayed]

@sfmskywalker I am totally new to Elsa, do we have a documentation on different tenanted users for Elsa studio and how to create them?
Also do we have different user roles or only Admin role?
I have checked Elsa v3 documentation but couldn't find much info

[sfmskywalker]

Hi @EngSayed , welcome to the community! There's no documentation about tenants or users and roles at the moment. Using the default Identity module, there is a possibility to define different users and roles other than admin user and admin roles, but you have to either configure these from appsettings.json or via a REST API exposed by the Identity module. All of this has yet to be documented, until then your best bet is to explore the source code to find the API endpoints and or by looking at the Elsa.Server.Web reference application in this repo.