Libraries are shared between org units and tenants by default

studio
suggestion

#1

Hello -

One of the features of 2018.3 is the ability to publish re-usable component which is great… However the library uploaded in one tenant and org unit is shared across all tenants and org units of the orchestrator which is a concern…

If the tenants setup are Dev and QA, library uploaded in one tenant is available in the other tenant by default and will interfere with the testing. Also if the library is shared between org units, it is a security concern, as we wouldn’t want to expose business logic of one Org unit with other Org unit.

Did anyone else observe this behavior? If so, how did you overcome such scenario?

Thanks,
Teja


#2

Yeah, per tenant library is planned.


#3

Per Org Unit Library would be even better…

We don’t want to be sharing the libraries between Org Units as well for security reasons…