The version determines the plugins, themes and language files that are available for your tenants. So if the version where the tenant runs on does not contain the plugin, the tenant will not show the plugin.
The version determines the plugins, themes and language files that are available for your tenants. So if the version where the tenant runs on does not contain the plugin, the tenant will not show the plugin. Activating the plugin on the version will only make it active for new tenants created using a snapshot based on the version which contains the plugin and has it activated. To create a new snapshot, you can hit deploy on your version.
Versions are the environment your tenants run in. You can move tenants from one version to another to update that environment. This gives you the opportunity to test new functionality on a new version, without changing your existing tenants. The deploy step is the action that updates the multi-tenant environment. Thus, you can make the plugin available to your tenants by moving one, or all, to the new version after you've created a deploy for that version.
However, if tenants have been provisioned by our WaaS plugins, the WaaS-Client plugin determines which plugins are turned on and off. One way to make sure that for tenants the plugin is enabled, is to edit the "role" on your version to activate the plugin on the version in the WaaS Client settings. After you've deployed that, and moved a tenant over to the new version, the plugin should be activated, given it has a role for which the plugin is active.
The storefront creates tenants on what we call your production version. You can see which version is your production version by the green pill next to the Version name.