As someone who is also responsible for the protection of user data, this is a big NO from me as long as the user cannot deactivate it from his profile or it can be deactivated for the instance all together.
There are laws limiting this in large parts of the world, and this can be a large project crasher if it's not optional.
Would you oppose it even if it was an admin only function?
When I get ready for upgrades I tell users to get off the system at a certain time but some forget. It would be nice as an administrator to see who is still logged in and call them to tell them to save their work before I lock them out.
I see your point (and everyone else's), but it is important that this functionality can be deactivated.
KarlMetum KarlMetum, can you add this to your idea (being able to deactivate this function)? I think this might increase support for your idea (mine at least )
You could add a custom field to the employees or user record which says "I want to be tracked" or "I agree to be tracked".
Add this field to the profile view.
Then you can switch on session tracking in the admin section.
With that data you can write a simple custom dashlet (perhaps with a custom API call) which shows all tracker_session entries with date_end=null and the above flag enabled.
What happens if your session expires, I do not know, perhaps you stay online until the end of days.
This is a must, I think. There was some discussion about ways to do this presence check -> Online (logged in) presence? but the OPI ruins that method. So yeah, when do we get this feature in Sugar?
There is a very old (March 2014) Enhancement Request outstanding -> 68059
Seem´s like that richer tracker functionality Francesca Shiekh knew from v6 was removed in 7.1.6 or earlier.
Retrieving data ...