Skip to content
LogScale Self-Hosted Deployment
This is an archived version of the documentation downloaded from LogScale Documentation Archives. Up to date documentation, and documentation for later versions, is available on LogScale Documentation

## Enabling and Disabling Feature Flags

LogScale features can be enabled or disabled through three different methods: configuration settings in the initialization file, GraphQL mutations on a running service, or using the humioctl command-line interface. Each method offers different advantages, with configuration settings requiring service restarts, mutations allowing real-time changes, and humioctl providing command-line control for global, user-level, or organization-wide feature management.

Some features are not enabled by default within LogScale and must be switched on.

This can be achieved in two ways:

- Using Configuration Settings – requires changing the configuration and restarting the service

- Using Mutations – enabled through a GraphQL mutation on a running service

- Using humioctl – enabled through a GraphQL mutation through the command line tool Command-Line Interface (humioctl)

### Using Configuration Settings

You can enable feature flags within the configuration file for LogScale using the `INITIAL_FEATURE_FLAGS` variable. To enable a feature, you must prefix its name with a `+` and to disable use `-`. For example:

ini

    INITIAL_FEATURE_FLAGS=+UserRoles,-UsagePage

### Using Mutations

Using a mutation to enable the feature means that the configuration and service do not need to be restarted to gain access to the new feature. It is good practice if you find the feature useful to enable it in the configuration file in addition to the mutation.

To enable a particular feature, you can submit the following request through your chosen API tool or the Accessing GraphQL using API Explorer.

graphql

    mutation {
      enableFeature(feature: PermissionTokens)
    }

The response will confirm the feature has been enabled:

json

    {
      "data": {
        "enableFeature": true
      }
    }

Features can be disabled with a different mutation:

graphql

    mutation {
      disableFeature(feature: PermissionTokens)
    }

Which returns a confirmation that the item has been disabled:

json

    {
      "data": {
        "disableFeature": true
      }
    }

#### Using humioctl

Features can be enabled and disabled using humioctl.

To enable a feature, use the `feature-flags` option. Depending on the feature you may be able to enable the feature globally, for a user, or an entire organization.

For example, to enable `PermissionTokens` globally:

shell

    $ humioctl feature-flags enable --global PermissionTokens

Which returns confirmation:

shell

    Enabled feature "PermissionTokens" globally

To disable a feature:

shell

    $ humioctl feature-flags disable --global PermissionTokens

Which returns confirmation:

shell

    Enabled feature "PermissionTokens" globally

#### Enter search term