Hi WeiMing, sure.
So in order to have a more granular tree system for separating customers/sites/devices I am thinking something like this below, so an Org equates to a partner, for example we have partners with customers under them, and direct customers under a specific org, under that we create customer groups, what we can end up with it a customer group with a lot of devices in one view.
This helps organise the view for admins and end customers down to specific sites, if the reporting could also be done at a site level as well it would be great (so the DB only reports back on the devices in that site sub group)
Something like this:
Top level list of Orgs
├─ Org 1 (eg: Partner X customers)
│ └─ Customer name (eg: Fred Smith Ltd)
│ └─ Site name (eg: London HQ)
│ └─ device 1 (eg: Max HD4)
└─ Org 2 (eg: Partner Y customers)
└─ Customer name (eg: Joe Bloggs Ltd)
└─ Site name (eg: London HQ)
└─ device 1 (eg: Max Transit Duo)
└─ device 2 (eg: AP One Enterprise)
Logon security as is now by Org and group, that way we can give a partner access to all their customers under that org, but also by group so we can give individual customers access to their company group and devices/sites underneath (I cant see we’d ever need security access to individual sites)