This weekend we pushed an update that improves the accuracy of the “People on this project” block in the sidebar on a project’s overview screen.

The block used to list someone’s last login time, but if people had their login information stored by their web browser then the last login time could have been weeks ago even if they just accessed a project seconds ago.

The change does away with this inconsistency. Instead of “last login” we now show “latest activity.” This way if someone logged in a few days ago, but just accessed a project a few minutes ago, we can show an accurate “few minutes ago” access in the list.

If someone hasn’t accessed the site for 30+ days, then we say “Hasn’t logged in recently.” Important Exception: Part of this update required that we reset the tracking information so everyone that hasn’t accessed the site since Feb 24th will be marked as “Hasn’t logged in recently.

This update also makes this data accurate on a per-project basis. The data used to be based on an access to any project in your account. So if someone accessed Project A, and you were looking at Project B’s overview screen, you’d see a last access update in Project B even though the person didn’t access Project B. This update changes that. Each project overview screen shows activity for that project, not all projects.

Thanks again for your continued support and feedback. This change is based on that feedback, so keep it coming.

Sweet! This is what we were hoping for – it’ll solve one our frustrations. Thanks for the update!

Time will tell on this. It has pros and cons, like most change does. Knowing activity on a per-project basis, for example. Could be good when you’re trying to judge if someone is aware of a particular event. Not so good when you want to know, in general, when a user last logged in – without the need to hunt through project-by-project. Pro and Con.

Another example: “not recently” is a bit too vague, I think. I don’t equate “recently” with a 30-day timeframe. Plus, it’s often meanngful to know the difference between “not logged in for 42 days” versus the evened-out “not recently.”

Thanks for the update! This is very helpful for our company!

Sweet – thanks for making an important refinement for improving communication. The only situation that I can see where the current callouts are misleading is if someone has never logged in, it says “Hasn’t logged in not recently”. Maybe then the report should be, “still needs to create account” or “has never logged in” I still need to know who to nag :)

I’d also like to know which users didn’t logged in yet.
Please change this report to ‘has never logged in’ or something.

Thanks,
Jef

I agree with the last post. I really would like to know who has never logged in so I can follow up and see why they haven’t and perhaps help them.

You say that people who haven’t accessed for more than 30 days get ‘Hasn’t logged in recently’ line under them. Why not just show when last activity was no matter how long ago. ‘Lastest activity xx days ago’.
Maybe the ‘Hasn’t logged in recently’ should be a temporary measure for people who you don’t know when they last accessed the project. Other new users should have the ‘Has not logged in yet’, I think.

I like the new system but would also like to be able to see, as before, who has not logged in at all.

Agree about the “not logged in yet” comment. In fact, up until you changed this, I was using this to track which team members hadn’t logged in yet. Ironically, those are the ones who are complaining about the lack of collaboration. Now I have nothing to show them.

Please at least put this part back.

Exactly the same for my team. Knowing who has never logged in is very important for us for all of the reasons mentioned in the posts above. The loss of this will cause us a few problems, and adding this back in would be be much appreciated.

I’ve just been playing with this and unless I post something into a project, basecamp doesn’t seem to be capturing me having been in there? For a lot of our clients we get them to go into the site to get the latest information, but they may not actually post anything. For these people we can end up thinking they haven’t logged in (no recent activity) when actually they have. I may be missing something, but for us the previous system worked a lot better.

You can use the 30 day basis to tell if someone isnt using the system. If some one hasn’t logged in, in the past 30 days, then that tell you they arent using the system. Im on people who havent logged in everyday. I can see how some people might need the never logged in, but with the amout of information that we put in, 30 days without using Basecamp, is just the same as never.

The new user issue doesnt seem to be as bad as sounds. If the new user says ‘Hasn’t logged in recently’ after a few days of adding them, then this tell you again that they havent used the system.

Maybe its the reset in all logins that are causing the issue. Give it 30 days for the system to collect everyones logins and see how the new system works then

Please return the functionality for displaying “Never Logged In”. It is very important for us to know when participants have not accessed the site at all.

i have to agree, i really liked the old way users were tracked… now it just looks like no one is checking or logging in and i know they are.

We still miss the “Never Logged In” status and wonder why only the last 30 days are displayed. Why not say “Latest Activity” regardless of number of days. That would be more meaningful than what we have now.
Thanks