--- title: "Sorting your systems dynamically" slug: "sorting-your-systems-dynamically" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T17:46:02Z published: 2026-09-07T17:46:02Z canonical: "docs.trellix.com/sorting-your-systems-dynamically" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Sorting your systems dynamically You can dynamically sort your systems into your ePO - On-prem **System Tree** using a combination of system criteria and other elements. ### Creating the basic groups Sorting dynamically requires that you create some basic groups for your tree structure. For smaller organizations, your **System Tree** might not be complex and contain only a few groups. For larger organizations, we recommend that you create some groups similar to these sample designs: - **GEO** — Geographic location - **NET** — Network location - **BU** — Business unit - **SBU** — Subbusiness unit - **FUNC** — Function of the system (web, SQL, app server) - **CHS** — Chassis (server, workstation, laptop) ### Selecting and ordering the basic groups After you decide on the basic building blocks for groups in the **System Tree**, you must determine which building blocks to use and in which order based on these factors: - **Policy assignment** — Do you have many custom product policies to assign to groups based on chassis or function? Do certain business units require their own custom product policy? - **Network topology** — Do you have sensitive WANs in your organization that a content update might easily saturate? If you have only major locations, this is not a concern for your environment. - **Client task assignment** — When you create a client task, such as an on-demand scan, do you need to do it at a *group level*, like a business unit, or *system type*, like a web server? - **Content distribution** — Do you have an agent policy that specifies that certain groups must get their content from a specific repository? - **Operational controls** — Do you need specific rights delegated to your ePO - On-prem administrators that allow them to administer specific locations in the tree? - **Queries** — Do you need many options when filtering your queries to return results from a specific group in the System Tree? After you choose the basics for your tree structure, create a few sample **System Tree** models and look at the pros and cons of each design. There is no right way or wrong way to build your **System Tree**, just pluses and minuses depending on what you choose. Here are a few of the most commonly used **System Tree** designs: - **GEO** -> **CHS** -> **FUNC** - **NET** -> **CHS** -> **FUNC** - **GEO** -> **BU** -> **FUNC**