diff --git a/src/content/docs/new-relic-solutions/business-observability/intro-pathpoint.mdx b/src/content/docs/new-relic-solutions/business-observability/intro-pathpoint.mdx
index 41ed484f13e..c26d866a42e 100644
--- a/src/content/docs/new-relic-solutions/business-observability/intro-pathpoint.mdx
+++ b/src/content/docs/new-relic-solutions/business-observability/intro-pathpoint.mdx
@@ -131,7 +131,7 @@ Each Pathpoint flow is divided into:
     * Green: Optimal performance. The related entity or alert is functioning as expected.
     * Yellow: Warning state. The related entity or alert has an active warning condition.  Some attention may be needed.
     * Red: Critical state. The related entity or alert has an active critical condition.  Immediate attention is needed.
-    * Gray: Requires attention. Potential configuration issues or data gaps exist, such as a missing alert or the telemetry is not available.
+    * Gray: Requires attention. Potential configuration issues or data gaps exist, such as a missing alert or the telemetry isn't available.
 
     Each Pathpoint step relies on one or more signals, making signal health crucial to overall Pathpoint performance. By tracking signal status, you can effectively monitor system health and quickly identify issues.
 
@@ -141,6 +141,7 @@ Each Pathpoint flow is divided into:
       Also, by default, Pathpoint will condense or hide some of the non-critical signal names. You can toggle on "expand all signals" to see all signal names.
     </Callout>
 
+
     ### View signal details [#view-signal-details]
 
     Signals linked to a New Relic entity adopt the entity's health status. Clicking a signal icon displays a window with detailed signal information, including:
@@ -174,6 +175,27 @@ Each Pathpoint flow is divided into:
 
 By tracking each of these components, Pathpoint provides a comprehensive view of how customers interact with an organization at every stage of their journey. This makes it possible to identify and diagnose issues quickly, optimize the customer experience, and make data-driven decisions to drive better business outcomes.
 
+### Understanding stage and step status [#stage-step-status]
+
+A stage will take on the status of its worst step. If a stage has 2 green steps and 1 red step, this stage will become red. That rule isn't configurable. However the step status rule is configurable.
+
+To view or configure your step's status rule enter edit mode and do the following:
+
+    1. Click on the ellipses to the right of step name that you want to configure, and select <DNT>**Settings**</DNT>
+    2. Under <DNT>**Status Configurations**</DNT> choose the rule that you want to use
+
+By default it uses <DNT>**Rollup the worst status**</DNT>. You can refine this by checking <DNT>**Apply only when**</DNT> and choosing a percentage of signals needed to change the step status. For example, you have 10 signals and want to change status at 50%. When 5 signals are either red or yellow, the status will change to reflect the worst status among the 5 unhealthy signals. Or a set count of signals needed to change the step status. For example, at least 2 of 5 signals must be unhealthy to change the step status.
+
+Also, you will be able to exclude certain signals from contributing to the status of the step. This allows you to delete noisy or known bad signals from impacting the status.
+
+You may also choose <DNT>**Rollup the best status**</DNT>.  Exactly as it sounds with this option the step will take on the status of its best signal.
+
+     <img
+      title="Step Status Configuration"
+      alt="Step Status Configuration"
+      src="/images/pathpoint_v2_status_configuration.webp"
+    />
+
 ## Create flows [#flows]
 
 In previous sections we described the main elements within the pathpoint UI: stages, steps, and touchpoints. In Pathpoint the highest level grouping of these elements is the _flow_. A flow is usually used to model a "business journey" or "customer journey". The stages of a flow represent higher level concepts that compose the journey. When we think about what kinds of stages to use it helps to think about what our business process or "journey" is and how we think of it in sequence. Often it helps to look at other flows within a similar industries. Examples of industries or verticals are:
diff --git a/static/images/pathpoint_v2_status_configuration.webp b/static/images/pathpoint_v2_status_configuration.webp
new file mode 100644
index 00000000000..e0147185abf
Binary files /dev/null and b/static/images/pathpoint_v2_status_configuration.webp differ