diff --git a/doc/source/internal/helpcenter_training/faq/faq_images/gate_label.png b/doc/source/internal/helpcenter_training/faq/faq_images/gate_label.png
new file mode 100644
index 0000000..ae52bed
Binary files /dev/null and b/doc/source/internal/helpcenter_training/faq/faq_images/gate_label.png differ
diff --git a/doc/source/internal/helpcenter_training/faq/how_can_the_docs_be_deployed_to_pre-prod_and_prod_and_who_will_be_the_responsible_to_do_that.rst b/doc/source/internal/helpcenter_training/faq/how_can_the_docs_be_deployed_to_pre-prod_and_prod_and_who_will_be_the_responsible_to_do_that.rst
index c7c6c09..535afad 100644
--- a/doc/source/internal/helpcenter_training/faq/how_can_the_docs_be_deployed_to_pre-prod_and_prod_and_who_will_be_the_responsible_to_do_that.rst
+++ b/doc/source/internal/helpcenter_training/faq/how_can_the_docs_be_deployed_to_pre-prod_and_prod_and_who_will_be_the_responsible_to_do_that.rst
@@ -3,3 +3,15 @@ How can the docs be deployed to PRE-PROD and PROD and who will be the responsibl
 =============================================================================================
 
 By triggering the label "**gate**" on gitea/github the respective automated jobs will trigger final merge and build of the documentation as well as publishing of the documentation to respective portal (PREPROD/PROD). Responsibility can be addressed to the labelling permission. Remaining stuff is in hands of zuul automation.
+
+**Prerequesits to set the Gate label:**
+
+1) Confirmity check of Zuul is successful (Zuul approval).
+2) Approval of Pull Request by Squad member is there.
+
+If one of these prerequesits is not there. The Zuul pipeline will not start to work and to release the document.
+
+**How to set the Gate label:**
+
+.. image:: faq_images/gate_label.png
+