diff --git a/docs/flows/versioning.mdx b/docs/flows/versioning.mdx
new file mode 100644
index 0000000000..e497d95025
--- /dev/null
+++ b/docs/flows/versioning.mdx
@@ -0,0 +1,18 @@
+---
+title: "Version History"
+icon: 'clock'
+description: "Learn how flow versioning works in Activepieces"
+---
+
+Activepieces keeps track of all published flows and their versions. Here’s how it works:
+
+1. You can edit a flow as many times as you want in **draft** mode.
+2. Once you're done with your changes, you can publish it.
+3. The published flow will be **immutable** and cannot be edited.
+4. If you try to edit a published flow, Activepieces will create a new **draft** if there is none and copy the **published** version to the new version.
+
+This means you can always go back to a previous version and edit the flow in draft mode without affecting the published version.
+
+![Flow History](/resources/flow-history.png)
+
+As you can see in the following screenshot, the yellow dot refers to DRAFT and the green dot refers to PUBLISHED.
diff --git a/docs/mint.json b/docs/mint.json
index 951b1beb29..22146ddc92 100755
--- a/docs/mint.json
+++ b/docs/mint.json
@@ -150,7 +150,8 @@
         "flows/building-flows",
         "flows/passing-data",
         "flows/publishing-flows",
-        "flows/debugging-runs"
+        "flows/debugging-runs",
+        "flows/versioning"
       ]
     },
     {
diff --git a/docs/resources/flow-history.png b/docs/resources/flow-history.png
new file mode 100644
index 0000000000..854e06a288
Binary files /dev/null and b/docs/resources/flow-history.png differ