FMEPRD-385 Add FME Steps in CD Pipelines Beta Documentation + Release Note (#100743)

* 50559a Release Note Nits

* 50b2e4 Update YAML Example

* 7f94d9 SME Review

* 4f4688 Consolidate Links

* a0b43a Formatting Nit

* 84a3bf Add Permissions + Additional Platform Sections

* 52f72d Fix Link

* 1c2582 Lint Tooltips

* 2167cd Merge branch 'main' into add-fme-pipelines-beta-docs

* 7a6ba4 Doc Review

* f9befc Merge branch 'main' into add-fme-pipelines-beta-docs

* fa6b92 Bump Release Date

* 63cc62 Harness FME pipelines - polishing iteration 3

* 032008 Harness FME pipelines - polishing iteration 2 - finish visual section

* 40b1b3 Harness FME pipelines - polishing iteration 1

* 600730 tweaks to tooltips

* 4aa428 Don't Have This Yet

* bc2ded Merge branch 'main' into add-fme-pipelines-beta-docs

* af6573 Doc Review

* 94dca2 FMEPRD-385

Author: alai97

docs/continuous-delivery/cd-onboarding/integrating-cd-other-modules.md

@@ -7,6 +7,15 @@ redirect_from:
   - /docs/continuous-delivery/get-started/integrating-cd-other-modules
 ---
 
+<CTABanner
+  buttonText="Request Access"
+  title="FME Steps in Pipelines is in beta!"
+  tagline="Add Harness Management & Experimentation steps to your Harness CD pipelines at the stage level. Available now in beta!"
+  link="https://developer.harness.io/docs/feature-management-experimentation/fme-support"
+  closable={true}
+  target="_self"
+/>
+
 This topic describes a few of the cross-module use cases in the Harness platform.
 
 ## Harness Continuous Integration
@@ -154,3 +163,18 @@ For a longer tutorial of Harness CI and CD integration, go to [End-To-End CI/CD
 ## Harness Chaos Engineering
 
 The [Harness Chaos Engineering (HCE) integration with Harness CD](/docs/chaos-engineering/integrations/cicd/harness-cd) allows chaos experiments to be executed as part of a Harness CD pipeline.
+
+## Harness Feature Management & Experimentation
+
+You can integrate [Harness Feature Management & Experimentation](/docs/feature-management-experimentation/) into your [Harness CD pipelines](/docs/feature-management-experimentation/pipelines) to manage feature flags as part of your deployment workflow.
+
+By adding FME steps to CD stages, you can create, update, target, and disable feature flags during a pipeline execution. This allows feature flag operations to be versioned, reviewed, and executed alongside application deployments, reducing manual steps and improving release coordination.
+
+You can integrate Harness FME with CD pipelines in the following ways:
+
+- Creating or updating feature flags as part of a release
+- Managing individual targeting lists during staged rollouts
+- Adjusting default traffic allocations when deploying a new version
+- Killing a feature flag immediately in response to deployment issues
+
+For more information, see the [Pipelines documentation](/docs/feature-management-experimentation/pipelines/).

docs/feature-management-experimentation/pipelines/index.md

@@ -1,7 +1,7 @@
 ---
 title: Feature Management & Experimentation release notes
 sidebar_label: Feature Management & Experimentation
-date: 2026-01-16T10:00:00
+date: 2026-01-23T10:00:00
 tags: ["fme", "feature management experimentation"]
 sidebar_position: 11
 ---
@@ -12,10 +12,33 @@ import HarnessApiData from '../src/components/HarnessApiData/index.tsx';
 
 These release notes describe recent changes to Harness Feature Management & Experimentation (FME).
 
-#### Last updated: January 16, 2026
+#### Last updated: January 23, 2026
 
 ## January 2026
 
+### [New Feature] FME Steps in Harness Pipelines is in Beta
+----
+#### 2026-01-23
+
+Harness FME steps in pipelines is now in beta, allowing you to manage feature flags directly within your deployment workflows. You can add FME steps to [custom stages](/docs/platform/pipelines/add-a-stage/#add-a-custom-stage) and perform feature flag operations as part of a single, auditable pipeline. 
+
+![](./static/fme/pipelines.png)
+
+You can add FME steps in Harness pipelines to automate and standardize the following operations, for example:
+
+- Create and update feature flags as part of a deployment
+- Manage individual targets deterministically, including setting or modifying explicit target lists during a rollout
+- Control default traffic allocation for staged or percentage-based rollouts
+- Disable a feature flag using a kill step
+- Coordinate deployments and feature flag changes in a single workflow, reducing manual configuration and operational risk
+
+These steps run alongside standard pipeline steps and logic such as approvals, failure strategies, waits, and notifications. To request access to the FME steps in Harness pipelines beta experience, contact [Harness Support](/docs/feature-management-experimentation/fme-support).
+
+#### Related documentation
+
+- [FME Steps in Harness Pipelines](/docs/feature-management-experimentation/pipelines)
+- [Integrating CD with other Harness modules](/docs/continuous-delivery/cd-onboarding/integrating-cd-other-modules/)
+
 ### [New Feature] Web support in the Flutter Plugin
 ----
 #### 2026-01-16