diff --git a/advanced/relative-paths.md b/advanced/relative-paths.md
index 8582c8bf..ae0ec4dd 100644
--- a/advanced/relative-paths.md
+++ b/advanced/relative-paths.md
@@ -1,6 +1,12 @@
 # How Relative Path Support Works in Portainer
 
-The relative path volumes support in Portainer is intended to provide you with a way to reference files and directories that are supplied within the Git repository alongside your compose file without needing to know the absolute path at which they will appear when they are deployed to your environment. In the background the way this works is as follows:
+The relative path volumes support in Portainer Business Edition is intended to provide you with a way to reference files and directories that are supplied within the Git repository alongside your compose file without needing to know the absolute path at which they will appear when they are deployed to your environment. 
+
+{% hint style="info" %}
+Relative path support is only present in Portainer Business Edition, and needs to be [enabled when deploying your stack from Git](../user/docker/stacks/add.md#relative-path-volumes) for this article to apply.
+{% endhint %}
+
+In the background the way this works is as follows:
 
 1. In Portainer, a stack deployment is initiated where the stack is located in a Git repository, **Enable relative path volumes** is selected and a **Local (or Network) filesystem path** is specified.
 2. Portainer creates a temporary unpacker container that bind mounts the path specified in the Local (or Network) filesystem path field.