Enable Multi-Tenancy for Globals

[eilidhhyslop-fmp]

Right now, the Multi-Tenancy Plug-In works with Collections but not with Globals.

From a design point-of-view, it doesn't appear to make sense to prevent a Singleton (a Global) from using Multi-Tenancy.

An example given in the documentation for use of a Global is a site navigation. I think this is a perfect example to illustrate why Multi-Tenancy should be available, as a use case is a different Tenant for a different site. In these cases, each site would need its own navigation. Therefore, it makes sense for Globals to be available on both multiple locales (which they already are) and multiple Tenants (which is missing functionality atm).

[mikefaust-jm]

You can use a collection as a singleton with the multi tenancy plugin. Just set isGlobal to true.

multiTenantPlugin<Config>({
  collections: {
    pages: {},
    layouts: {
      isGlobal: true,
    },
  },
}),

[eilidhhyslop-fmp]

I'm aware of this workaround, but ultimately you're still creating a document intended to be a singleton as a Collection. While it's currently possible, it seems like very poor practice to explicitly have a type available for singletons (Globals) but then not be able to use it normally.