---
title: "Feature Manager"
description: "Control which Wallet API v2 features are enabled at service startup using the feature manager."
stack: "Community Stack (open source) — version 1.1.1"
stack_version: "1.1.1"
stack_comparison: https://docs.walt.id/community-vs-enterprise.md
canonical_url: https://docs.walt.id/community-stack/wallet2/configurations/feature-manager
generated: 2026-10-01
---
# Feature Manager

Use the feature manager to control which Wallet API v2 features are enabled at service startup. This reduces complexity and the risk of misconfigurations.

## Feature Types

The feature manager offers two types: **Base** and **Optional**.

### Base Features

Base features are always enabled and provide critical functionality expected to be available by default. For the Wallet API v2, the core `wallet-service` is a base feature.

### Optional Features

Optional features can be enabled or disabled based on your requirements.

1. **Enabled by default**: work without additional configuration.
2. **Disabled by default**: must be explicitly enabled in `_features.conf`, and may require their own configuration file.

**Note:**

Each feature may have zero, one, or multiple configuration files associated with it.

## How the Feature Manager Works

1. **Initialisation with Feature Catalogs**: the service is passed its feature catalog on startup.
2. **Determination of Active Features**: the initializer resolves which features are explicitly enabled or disabled, and the default state of the rest.
3. **Loading Configurations**: only the configurations for base features and explicitly enabled optional features are loaded.

**Note:**

The service must be **restarted** for feature-flag changes to take effect — there is no hot reload.

## Feature Configuration

Configure features by editing `_features.conf`, as explained in [Features](https://docs.walt.id/community-stack/wallet2/configurations/config-files/features.md).