# Are the designer/task webapps multi tenant enabled?

**URL:** <https://forum.flowable.org/t/are-the-designer-task-webapps-multi-tenant-enabled/3251>\
**Category:** Flowable Engine\
**Created:** [January 16, 2019, 5:14pm UTC](https://forum.flowable.org/t/are-the-designer-task-webapps-multi-tenant-enabled/3251 "2019-01-16T17:14:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jckermagoret](https://avatars.discourse-cdn.com/v4/letter/j/34f0e0/32.png) [@jckermagoret](https://forum.flowable.org/u/jckermagoret)\
**Post date:** [January 16, 2019, 5:14pm UTC](https://forum.flowable.org/t/are-the-designer-task-webapps-multi-tenant-enabled/3251/1 "2019-01-16T17:14:09Z")

</div>

Hello,  
I read in a few posts tenancy seems to be operational but it’s not clear at which level.

Is it possible to set tenant for users so they only see:

- in the modeler webapp: processes related to their tenant
- in the task webapp: tasks and processes related to their tenant

Is it available out of the box? Does it need to update the database? Add a column?

Thanks

JC

---

<div class="post-metadata">

**Author:** ![jckermagoret](https://avatars.discourse-cdn.com/v4/letter/j/34f0e0/32.png) [@jckermagoret](https://forum.flowable.org/u/jckermagoret)\
**Post date:** [January 21, 2019, 5:08pm UTC](https://forum.flowable.org/t/are-the-designer-task-webapps-multi-tenant-enabled/3251/2 "2019-01-21T17:08:41Z")

</div>

Any ideas about this question?

Thanks

---

<div class="post-metadata">

**Author:** ![Robinyo](https://avatars.discourse-cdn.com/v4/letter/r/dec6dc/32.png) [@Robinyo](https://forum.flowable.org/u/Robinyo)\
**Post date:** [January 23, 2019, 8:45pm UTC](https://forum.flowable.org/t/are-the-designer-task-webapps-multi-tenant-enabled/3251/3 "2019-01-23T20:45:59Z")

</div>

See:

- [Multi-tenancy support for Flowable Modeler app](https://forum.flowable.org/t/multi-tenancy-support-for-flowable-modeler-app/1434/2?u=robinyo)
- [Flowables Docs - Multitenancy](https://www.flowable.org/docs/userguide/index.html#advanced.tenancy)
- [Flowables Blog - Multitenancy](https://blog.flowable.org/2018/09/11/multitenancy-in-flowable/)

---

<div class="post-metadata">

**Author:** ![ruzkant](https://avatars.discourse-cdn.com/v4/letter/r/7ea924/32.png) [@ruzkant](https://forum.flowable.org/u/ruzkant)\
**Post date:** [January 28, 2019, 7:57am UTC](https://forum.flowable.org/t/are-the-designer-task-webapps-multi-tenant-enabled/3251/4 "2019-01-28T07:57:06Z")

</div>

Multi tenancy is mainly well supported on the engine and API level.

The modeler app however can be configured to support multi tenancy. Out of the box you have to configure a specific tenant\_id for the modeler app, which means you need to deploy an instance per tenant in that scheme.

This was the pull request:

> <https://github.com/flowable/flowable-engine/pull/914>

You set the flowable.common.app.tenant-id property in the application properties:

> <https://github.com/flowable/flowable-engine/blob/eeebfd23af3571741b60e3f663f17c0ecc50a812/modules/flowable-ui-modeler/flowable-ui-modeler-app/src/main/resources/flowable-default.properties>

If you are willing to modify the modeler code you can create your own implementation of the org.flowable.app.tenant.TenantProvider interface to determine the tenant id. (For me I have my own distribution of the app that uses keycloak for user authentication and authorization and built my own tenant provider accordingly)

To the best of my knowledge the task app does not yet support multi tenancy out of the box. At some point I saw that tenant\_id has been added as a column to the user table in the idm app, so I expect some contribution could be made there to pull that into the modeler and task apps, or maybe they have it in the pipeline…