Groups and multi-country: your real structure, in software

What groups do

• Nest countries, cities, hubs, fleets and client accounts in one tree.
• Set an expected vehicle count per node, so gaps between plan and reality are visible.
• Scope users to a node: a hub lead sees the hub, a country manager sees the country.
• Scope vehicles, assets, zones and service requests to the same nodes.
• Roll numbers up the tree for reporting without re-tagging anything.

How it works

1. Step 1

   Draw the tree

   Create country nodes, then hubs beneath them, then fleets or client accounts where you need them.

2. Step 2

   Place the fleet

   Vehicles, batteries and keyfobs are assigned to the node that actually holds them.

3. Step 3

   Assign people

   Each user gets a role scoped to a node; access to everything below follows automatically.

4. Step 4

   Operate per node

   Zones, service requests and alerts stay inside the node, so hubs are not flooded with each other's noise.

5. Step 5

   Report up

   Dashboards aggregate from vehicle to hub to country without extra work.

Who uses it

Data you get out

• Vehicle counts per node against the expected count.
• Utilisation, downtime and service volume aggregated per hub, fleet and country.
• User and permission list per node for access reviews.
• CSV export and API access at any level of the tree.

Related modules

User management assigns the roles, Zone Guard attaches zones to nodes, and BI dashboards read the tree to produce per-country reporting. Operators run this structure across 7 European countries today.