Feature flags

Hub frontend feature flags control which pages, controls, and optional data sources are available to users. They do not grant permissions and they do not start backend services. Roles and resource authorization still apply after a feature is visible.

This page covers every product-facing boolean flag understood by the current Hub frontend and the related backend switches operators commonly need with them. Infrastructure toggles such as TLS, telemetry, ingress, persistence, and storage-provider settings remain in the Helm chart reference because they configure the deployment rather than a Hub product feature.

For Helm installations, set flags below kerberoshub.frontend.features in your values file. The chart renders them as environment variables for the frontend container, and its startup script writes them to window.env.

kerberoshub:
  frontend:
    features:
      case:
        enabled: "true"
      videoEdits:
        enabled: "true"
      faceRedaction:
        enabled: "true"
        classifierTracksEnabled: "false"

Use quoted "true" and "false" values for frontend flags unless the chart field is documented as a native boolean.

General and navigation

Organisations and projects

The organisation and project flags form a hierarchy:

1. When organisations.enabled is explicitly "true" or "false", it controls the complete organisation feature family, including projects.
2. When organisations.enabled is empty, organisation child flags apply independently and projects.enabled becomes the project-group switch.
3. When both group flags are empty, the individual project child flags apply.

Live view

liveStreamMode, defaultStreamMode, paginationMode, pageSize, and maxStreams configure behavior but are not on/off feature flags. See the chart values for those settings.

Video editing and face redaction

These flags expose frontend controls only. Rendering redacted recordings still requires the redaction workflow and worker to be configured.

Media filters

Visible media-filter controls default to "true". Disabling one removes that filter control; it does not delete or change existing data. markerOptionsByDate.enabled is a behavior flag and defaults to "false".

media.filter.defaultView selects the initial media view and is not a boolean feature flag.

Runtime-only frontend flags

The frontend understands the following environment variables, but the current Hub chart does not expose matching values in kerberoshub.frontend.features. They require custom deployment wiring until chart support is added.

OPENAI_ENABLED is supplied by the chart’s top-level openai.enabled value. It enables frontend semantic-search integration and requires the corresponding backend configuration.

Backend and deployment switches

These switches are related to features but are not frontend flags:

Some components use replica counts rather than an enabled flag; setting replicas to zero disables those deployments.

Known exposure gaps

• The frontend consumes FEATURE_DARK_MODE_ENABLED, while the current chart template emits FEATURE_DARK_MODE. Until those names are aligned, kerberoshub.frontend.features.darkModeEnabled does not reliably control the frontend through the standard chart.
• Runtime-only flags listed above are valid frontend inputs but are not currently mapped by the Hub chart.
• A visible control never replaces backend authorization. Users still need the required role, permissions, organisation membership, and project scope.

Applying changes

After changing Helm values, upgrade the release and allow the frontend pod to restart so its startup script regenerates env.js.

helm upgrade hub kerberos/hub \
  --namespace kerberos-hub \
  --reuse-values \
  --set-string kerberoshub.frontend.features.faceRedaction.classifierTracksEnabled=false

For GitOps installations, commit the value change to the environment repository instead of running helm upgrade directly.