> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/home-cloud-user-manual/working-with-org-trees.md).
# Working with Organization Trees
EnGenius Cloud adopts an organization tree structure to let user define the scope of their managed networks. All device managing or monitoring functions can be applied to different scopes as laid out in the user's tree. That gives VAR or MSP users great flexibility in managing their networks.
The current organization tree structure consists of three levels, from largest to smallest:
* Organization - A grouping of one or more hierarchies under the umbrella of a single license.
* Hierarchy View - A cluster of networks, which may be geographically concentrated or spread out.
* Network - A set of network devices united by a single configuration set.
The organization tree definition is shown on the top left corner of the web GUI as follows:
## **How-to Videos**
### **How to build your company networks in EnGenius Cloud**
[**https://www.youtube.com/watch?v=sN2y44Yzi7s\&feature=youtu.be\&t=5**](https://www.youtube.com/watch?v=sN2y44Yzi7s\&feature=youtu.be\&t=5)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://doc.engenius.ai/home-cloud-user-manual/working-with-org-trees.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.