> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/feature-management-experimentation/use-fme/config-management.md).

# Config Management

Learn how to manage runtime application configuration with Harness Configs.

Config Management is available when the Configs feature is enabled for your project. When it is enabled, **Configs** appears in the Harness FME navigation.

Harness Configs are standalone, versioned runtime configuration objects. Config Management supports configurations for general application settings as well as AI-related settings such as prompts and model parameters, which can be managed independently and governed through Harness FME.

```mermaid
flowchart TB

    APP["Your Application"]:::app
    SDK["Harness FME SDKs"]:::sdk

    APP --> SDK

    SDK --> FLAG
    SDK --> CONFIG

    subgraph FM["&nbsp;&nbsp;&nbsp;Feature Management&nbsp;&nbsp;&nbsp;"]
        direction TB

        FLAG["Feature Flags"]:::purple
        TARGET["Targeting"]:::purple
        TREAT["Treatments"]:::purple
        ROLLOUT["Progressive Rollouts"]:::purple

        FLAG --> TARGET
        TARGET --> TREAT
        TREAT --> ROLLOUT

        ROLLOUT --> RESULT1["Should this capability<br/>be available?"]:::result
    end

    subgraph CM["&nbsp;&nbsp;&nbsp;Config Management&nbsp;&nbsp;&nbsp;"]
        direction TB

        CONFIG["Configs"]:::purple
        SCHEMA["JSON Schema &<br/>Environment Values"]:::purple
        CTARGET["Targeting"]:::purple
        VERSION["Version History"]:::purple

        CONFIG --> SCHEMA
        SCHEMA --> CTARGET
        CTARGET --> VERSION

        VERSION --> RESULT2["How should this capability<br/>behave?"]:::result
    end

    classDef purple fill:#9b5de5,stroke:#9b5de5,color:#fff;
    classDef sdk fill:#5a67d8,stroke:#5a67d8,color:#fff;
    classDef app fill:#8110B5,stroke:#8110B5,color:#fff;
    classDef result fill:#16a34a,stroke:#16a34a,color:#fff;
```

Feature flags determine whether a capability is available to a target, while Configs determine how that capability behaves. Each config defines a JSON schema and one or more variations. A variation is a JSON value, and the schema is enforced: each variation must conform to the schema before you can save it, so your application only receives well-formed configuration. Each environment has its own values, which can be delivered statically or evaluated using targeting rules. Configuration changes can go through a review and approval flow, making it easy to review, audit, and promote changes over time.

![](https://1473625385-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrT2RGHAjtBTaObzchfpb%2Fuploads%2Fgit-blob-6dc4bdb946f3b8916a1d3939a74809fd4ca799cb%2Fconfigs-2.png?alt=media)

Harness Configs are evaluated through dedicated Configs SDKs and can coexist alongside Harness FME SDKs within the same application, allowing teams to separate release control from runtime configuration while managing both from a single platform.

## Get started

To get started with Config Management:

1. [Create a config](https://developer.harness.io/feature-management-experimentation/use-fme/config-management/setup.md) on the **Configs** page in Harness FME. The **Configs** page provides a centralized list of your configs where you can search by name and filter configs by tags and traffic types.
2. Configure its schema, variations, and targeting rules.
3. Initialize an environment, configure environment values, and add targeting rules.
4. Promote the configuration to additional environments as needed.
5. Integrate a [Configs SDK](https://developer.harness.io/feature-management-experimentation/new-to-fme/sdks-and-customer-deployed-components/server-side-configs-sdks.md) to retrieve values at runtime.

   See the [server-side Configs SDKs](https://developer.harness.io/feature-management-experimentation/new-to-fme/sdks-and-customer-deployed-components/server-side-configs-sdks.md) overview for the full list of supported languages. Client-side use cases are covered by the [client-side Configs SDKs](https://developer.harness.io/feature-management-experimentation/new-to-fme/sdks-and-customer-deployed-components/client-side-configs-sdks.md).
6. Monitor evaluations with Live Tail, and review change history with audit logs.

## Manage configs

After creating a config, you can return to the **Configs** page and search for configs by name, or filter configs using tags or traffic types.

![](https://1473625385-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrT2RGHAjtBTaObzchfpb%2Fuploads%2Fgit-blob-71958551b873e73ce55baa5bdd42b0e6ddf3acc8%2Fconfigs-3.png?alt=media)

Within a config, each environment has its own **Audit logs** tab, so you can see who changed what, when, and whether that change was published, requested, withdrawn, rejected, or failed. Search by editor or filter by change type and change status to track down a specific change.

## Governance

Config Management provides the following governance controls:

* **Role-based access control (RBAC):** Control who can view and change configs with the `FME_CONFIG` resource type. Go to the [resource type reference](https://developer.harness.io/harness-platform/use-harness-platform/platform-access-control/resource-type-reference#feature-management-and-experimentation) and the [FME permissions](https://developer.harness.io/harness-platform/use-harness-platform/platform-access-control/permissions-reference#feature-management-and-experimentation) to configure access.
* **Approvals:** Config changes go through a change proposal flow, where a change is submitted and then approved or rejected. Governance errors and warnings are shown when you submit a change.
* **Audit logs:** Every environment has an **Audit logs** tab that shows who changed what, when, and the status of each change. You can filter by change type, status, and column. Go to [Setup](https://developer.harness.io/feature-management-experimentation/use-fme/config-management/setup.md) to learn more.

{% hint style="info" %}
Pipeline-gated changes, where a Harness pipeline approves or rejects a change request, are available for feature flag and segment definitions in the new experience. They do not apply to configs. Go to [Pipeline-gated changes](https://developer.harness.io/feature-management-experimentation/management-and-administration/pipeline-gated-changes.md) to learn more.
{% endhint %}

## Experiments with configs

Experiments can use Config sources in addition to feature flag sources when this capability is enabled for your account. When it is enabled, you can select a config as the source when you create or edit an experiment, and configs appear in the experiments list. When it is not enabled, experiments are limited to feature flag sources. Go to [Cloud Experimentation overview](https://developer.harness.io/feature-management-experimentation/use-fme/experimentation/overview.md) to learn more about experiments.

## Further reading

For a deeper look at how Config Management helps teams manage runtime application behavior without redeploying applications, see:

* [Control runtime behavior with Config Management](https://harness.io/blog/control-runtime-behavior-with-config-management)
