The way most companies / organizations achieve this is to use authentication via 802.1x at the point of connection.   The identity used will be assocated with the device in question, in the Dashboard.  Of course, that's just a side-benefit for most customers, as it's mainly done to confirm who or what is connecting to their network and to provide fully secure WiFi comms.  Such identity is often also used to apply different policies to different users or user groups too;   i.e. what resources can they access?   how much bandwidth can they consume?   etc.   https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies Enterprise 802.1x is a pretty big project to undertake though, so best to explore this with an experienced Cisco partner, I would say.    ... View more