Latest Chrome / Pro
I am currently logged in, and several people on this list have also been logged in more recently than indicated. Marking this as critical because we have several critical external systems which depend on this info being up to date. (Actually think that's a strong case for this feature having tests)

~This is because the logic for updating a users last_seen property is handled when editing the user, which was happening implicitly in the previous auth flow.~
AFAICT - this was only updated when a user logged in which doesn't entirely reflect the name of this property.
~If we want this property to reflect the last time a user logs in, we should update the last_seen property after any successful check for the users password - that will ensure any future auth changes capture this too.~
EDIT: This property is updated for successful login attempts here: https://github.com/TryGhost/Ghost/blob/master/core/server/models/user.js#L780
If we want this to reflect the last time the user accessed ghost - we can add an updateLastSeen method to the user, and some middleware to the admin api that will call it when the api is access by a user.
It's definitely intended as last-seen/active, and _not_ last login
Most helpful comment
It's definitely intended as last-seen/active, and _not_ last login