Lansweeper is a as-requested or as-scheduled scanner, and it captures a point-in-time of the scan - i.e. if a user is logged on, it updates the user information as being logged on. So, if user B logs on later after the scan, it won't capture that unless user B is still logged on during the next scheduled scan.
Lansweeper does have the ability to scan event logs though, and the user logins/logoffs and locks/unlocks of computers are stored in the security event log... however, unfortunately you have to enable auditing on the security event log, which will increase the local event log sizes - and, you will have to tell lansweeper to collect event log entries for type = informational - which will also increase the database size (event logs table) in Lansweeper.
If you have a really small environment, you could probably get away with this. If larger, you will probably slow down lansweeper and bloat the event log table considerably. I think they warn you if you turn those on in the GUI.
For what its worth - a reference is here: https://stackoverflow.com/questions/11385164/eventviewer-eventid-for-lock-and-unlock
I would recommend using an active directory auditor/monitor such as ADAudit.
You could make a report on the asset + users and logon counts (though this not granular like I mentioned above) but it gives you a rough idea... reference: https://community.lansweeper.com/t5/forum/report-on-user-logins-multiple-assets/m-p/30329
-Rom