diff --git a/website/content/docs/concepts/connection-workflows/multi-hop.mdx b/website/content/docs/concepts/connection-workflows/multi-hop.mdx
index 8b1f0da83e..cfb3d6863b 100644
--- a/website/content/docs/concepts/connection-workflows/multi-hop.mdx
+++ b/website/content/docs/concepts/connection-workflows/multi-hop.mdx
@@ -68,7 +68,9 @@ intermediary workers have the following requirements.
 ### Ingress worker requirements
 
 To proxy target connections, ingress workers require outbound access to the
-Boundary control plane and inbound access from clients.
+Boundary control plane and inbound access from clients. 
+
+HCP Boundary clusters automatically deploy HCP-managed workers which can be used as ingress workers. Using HCP-managed workers as ingress workers is helpful when organizations have strict networks security policies that prohibit any inbound access. In this scenario, intermediary or egress workers within the private network can establish a reverse proxy connection to the HCP-managed ingress worker.  
 
 ### Intermediary worker requirements
 
@@ -84,4 +86,4 @@ upstream worker and outbound access to the destination host or service.
 
 ## Complete worker configuration
 
-For the full set of worker parameters and a complete configuration example, refer to the [worker stanza](/boundary/docs/configuration/worker) documentation.
\ No newline at end of file
+For the full set of worker parameters and a complete configuration example, refer to the [worker stanza](/boundary/docs/configuration/worker) documentation.