Feature availability

Feature availability is the organization-level view of whether an optional capability can be used now. It combines four signals:

• the feature exists in the current cloud or on-prem build;
• the organization is commercially or license entitled to use it;
• an organization administrator has not disabled it;
• the current member has the required role permission.

The settings page does not create entitlements and it does not add feature code to a deployment profile. It is a governed disable/re-enable surface for features that are already built and entitled.

Review a feature

Open Settings -> Features. The table shows each feature key, build state, entitlement state, effective access state, retained historical/evidence access, and any active administrator override.

Use search or the state filter to find features that are available, disabled by an administrator, not entitled, not in the build, or otherwise unavailable.

Disable a feature

Turn off an available feature and enter the required reason. Novantra records the override as organization-local evidence and immediately treats active use and writes as denied for that feature.

Historical and evidence reads are treated separately from active use. When a feature is disabled after use, records needed for audit, retention, and evidence review can remain readable through the owning module’s retained-access rules.

Re-enable a feature

Turn the feature back on and enter the reason. Re-enabling removes the active administrator override. The feature still has to be included in the build and commercially or license entitled before active use is restored.

Cloud and on-prem behavior

Cloud workspaces receive feature entitlement from the provider entitlement projection. On-prem workspaces receive feature entitlement from the signed license and per-organization entitlement projection. The organization settings surface is the same: administrators can only disable or re-enable eligible features.

Feature availability is not self-service billing, package purchase, or product-wide quota enforcement. Those are commercial and billing policy operations owned by provider-side modules.