What is the best way to centrally manage default enabled features for all tenants after initialization.

[rikbosch]

We're looking for a correct strategy to centrally manage enabled features for tenants, keeping in mind these will change in the future. The Default tenant has it's own feature set.

I know we can use setup recipe's to create the tenant and enable the features, but how would you enable a default feature after a tenant was initialized?

I can think of 2 options:

• Create 2 Default FeatureSet features, a Default Tenant FeatureSet and Tenant FeatureSet and use DataMigration to enable extra features.
• Just enable the features using code :

builder.Services
    .AddOrchardCms(orchardCoreBuilder =>
    {
           orchardCoreBuilder.AddTenantFeatures("Some.FeatureId");
    }

[MikeAlhayek]

OC already has a way to use the default tenant to manage the feature for other tenants. Something was added 8 months ago or so.

From the default tenant, list your tenants. Next to each tenant there is "Features" button that you can click and manage the features of that tenant. You can even disable the "Features" module for your tenant so you are the only one able to change their features.

[weirdyang]

How do you enable/disable features programmatically?

[hishamco]

ShellFeaturesManager.EnableFeaturesAsync("featuresToEnable");

[weirdyang]

thanks!

[weirdyang]

does this still work? the method seems to be asking for FeatureInfo class, and doesn't accept a string

[MikeAlhayek]

@weirdyang use the var feature = await featureService.GetAvailableFeature(id); method to get IFeatureInfo then use that to enable/disable features

[hishamco]

@rikbosch is this has been answered?

[rikbosch]

Not yet, but when I continue on this I'll add the strategy we picked here as well.