From 4d44fcb512e9b6766000a10fcbccb215bce899dd Mon Sep 17 00:00:00 2001
From: fermin831 <fermin.hernandez@artica.es>
Date: Tue, 21 Aug 2018 08:27:46 +0200
Subject: [PATCH] Added secondary groups documentation

---
 .../include/help/en/help_no_hierarchy.php     | 38 ++++++++++++++++++-
 .../include/help/ja/help_no_hierarchy.php     | 37 ++++++++++++++++++
 2 files changed, 74 insertions(+), 1 deletion(-)

diff --git a/pandora_console/include/help/en/help_no_hierarchy.php b/pandora_console/include/help/en/help_no_hierarchy.php
index 9d558bafae..352f4ab318 100644
--- a/pandora_console/include/help/en/help_no_hierarchy.php
+++ b/pandora_console/include/help/en/help_no_hierarchy.php
@@ -3,4 +3,40 @@
  * @package Include/help/en
  */
 ?>
-<h1>Hierarchy</h1>
\ No newline at end of file
+<h1>Hierarchy</h1>
+
+<p>
+We explained that the permissions of a group can be extended to the children by means of the configuration option <b>Propagate ACL</b>. However, from the user configuration, you can limit this functionality and prevent the ACL from propagating by checking No hierarchy.
+</p>
+
+<p>
+As a reference for the examples, we propose a configuration with two parent groups "Applications" and "Databases" with two children each, "Development_Apps" and "Management_Apps" for the former and "Databases_America" and "Databases_Asia" for the latter. Both parent groups are marked for ACL to spread.
+</p>
+
+<?php html_print_image("images/help/Acl_hierarchy_groups.png", false, array(
+    "style" => "max-width:100%"
+)); ?>
+
+<p>
+In the user edit view, if the following profiles are added:
+</p>
+
+<?php html_print_image("images/help/Acl_hierarchy_1.png", false, array(
+    "style" => "max-width:100%"
+)); ?>
+
+<p>
+The user will have access to the groups named "Applications", "Development_Apps", "Management_Apps" and "Databases".
+</p>
+
+<p>
+However, if a child of "Databases" is added:
+</p>
+
+<?php html_print_image("images/help/Acl_hierarchy_2.png", false, array(
+    "style" => "max-width:100%"
+)); ?>
+
+<p>
+Now the user will have access to the groups named "Applications", "Development_Apps", "Management_Apps", "Databases" and "Databases_Asia", but not to "Databases_America".
+</p>
diff --git a/pandora_console/include/help/ja/help_no_hierarchy.php b/pandora_console/include/help/ja/help_no_hierarchy.php
index 6771b0edf7..1970c9865a 100644
--- a/pandora_console/include/help/ja/help_no_hierarchy.php
+++ b/pandora_console/include/help/ja/help_no_hierarchy.php
@@ -4,3 +4,40 @@
  */
 ?>
 <h1>Hierarchy</h1>
+
+<p>
+We explained that the permissions of a group can be extended to the children by means of the configuration option <b>Propagate ACL</b>. However, from the user configuration, you can limit this functionality and prevent the ACL from propagating by checking No hierarchy.
+</p>
+
+<p>
+As a reference for the examples, we propose a configuration with two parent groups "Applications" and "Databases" with two children each, "Development_Apps" and "Management_Apps" for the former and "Databases_America" and "Databases_Asia" for the latter. Both parent groups are marked for ACL to spread.
+</p>
+
+<?php html_print_image("images/help/Acl_hierarchy_groups.png", false, array(
+    "style" => "max-width:100%"
+)); ?>
+
+<p>
+In the user edit view, if the following profiles are added:
+</p>
+
+<?php html_print_image("images/help/Acl_hierarchy_1.png", false, array(
+    "style" => "max-width:100%"
+)); ?>
+
+<p>
+The user will have access to the groups named "Applications", "Development_Apps", "Management_Apps" and "Databases".
+</p>
+
+<p>
+However, if a child of "Databases" is added:
+</p>
+
+<?php html_print_image("images/help/Acl_hierarchy_2.png", false, array(
+    "style" => "max-width:100%"
+)); ?>
+
+<p>
+Now the user will have access to the groups named "Applications", "Development_Apps", "Management_Apps", "Databases" and "Databases_Asia", but not to "Databases_America".
+</p>
+