diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/_index.md b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/_index.md
index 91e740ec647..235c363cd46 100644
--- a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/_index.md
+++ b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/_index.md
@@ -33,7 +33,7 @@ The elements of this category are described in the table below:
 | {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/parallel-split.png" alt="Parallel Split" class="no-border" >}} | [Parallel split](/refguide/parallel-split/)  | Adds two parallel paths to your workflow.                    |
 | {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/jump.png" alt="Jump Activity" class="no-border" >}} | [Jump](/refguide/jump-activity/)             | Allows you to jump to other activities in the workflow.      |
 | {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/wait-for-notification.png" alt="Wait for notification activity" class="no-border" >}} | [Wait for notification](/refguide/wait-for-notification/)             | Allows you to suspend a workflow’s execution until the workflow is notified.      | 
-| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event.png" alt="End event" class="no-border" >}} | End event                      | Ends the path of the workflow                                |
+| {{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event.png" alt="End event" class="no-border" >}} | [End event](/refguide/end-event/)           | Ends the path of the workflow                                |
 
 {{% alert color="info" %}}
 You can add customized activities to this section if you use the **Expose as a workflow action** setting in microflows. For more information see the [Expose as Workflow Action](/refguide/microflow/#expose-as-workflow-action) section in *Microflow Properties*.
diff --git a/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/end-event.md b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/end-event.md
new file mode 100644
index 00000000000..adb74065f95
--- /dev/null
+++ b/content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/end-event.md
@@ -0,0 +1,22 @@
+---
+title: "End Event"
+url: /refguide/end-event/
+weight: 50
+---
+
+## Introduction
+
+The **End Event** indicates where a workflow process ends.
+When the workflow execution reaches this element, the process is completed and no further actions are taken.
+Note that a workflow can have multiple end events, as shown in the example below:
+
+{{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event/multiple-end-events.png" alt="End Event Example" width="400" class="no-border" >}}
+
+The example shows a decision activity, where the workflow can take two different paths based on a condition.
+Each path leads to a different end event, either of which ends the process.
+In addition, there's an interrupting boundary event on one of the user tasks, with its own end event.
+In all of these cases, there's only one path that will be taken, and the process will end when it reaches the corresponding end event.
+
+## Properties
+
+The End Event properties does not have any properties.
diff --git a/static/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event/multiple-end-events.png b/static/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event/multiple-end-events.png
new file mode 100644
index 00000000000..2d9d316861d
Binary files /dev/null and b/static/attachments/refguide/modeling/application-logic/workflows/workflow-elements/end-event/multiple-end-events.png differ