When you install the application, you'll notice that it displays the apps based on the specific environment where you've installed it. For instance, if you set it up in your personal workspace, you'll only see your personal apps. Similarly, if you install it in a development environment, it will show you apps currently being developed. This distinction applies to testing and production environments as well. The organizational chart feature uses a free trial of a paid software tool. So, if you don't have a license, it's important to keep the logo as is and respect its promotional guidelines. This JavaScript library is very useful because it uses a simple JSON to build. 

When you click on the organizational chart, you can dive into detailed information about elements that are being used or act as dependencies. For example, you can see that in the TH layer, a module is being consumed, and specifically what you are consuming are fonts in .ttf and .otf formats. 

If you need to move the container of the organizational chart, you'll need to adjust a line of JavaScript found in: CWLayer/WB_OrgChart_Version8_Implemented/OrgChart_v8_Consumers(orDependencies)/GetHierarchicalTreeOnAfterFetch. In this line, "var chart = new OrgChart(document.getElementById("$b4")", notice "$b4", where "$b4" represents the automatically assigned ID that Outsystems gives to the container. It's important to note that if you relocate the container, its ID will change automatically, for example, to "$a1", and this will cause the orgchart feature to stop working. You can check this ID by right-clicking and inspecting the element in a Chrome browser.