That is correct. It is the last time that a user logged into the system and if blank that user has never logged in.

Regards,

Ronald

Yes.

The LastLoginDate attribute on the System.User entity stores the timestamp of the user’s most recent successful login.

So:

• If LastLoginDate has a value, it indicates the last time the user logged in successfully.
• If LastLoginDate is empty, it generally means the user has never logged in yet (for example, a newly created user account).

Note that the value is updated only after a successful authentication, so failed login attempts will not change this field.

If this resolves your question, please mark the answer as accepted so it can help others facing the same problem.

Hi Shogo ICHIKAWA

Yes mendix by default manages this login date and time stamp when ever a session and authentication to a user is done. So, if it is empty the user had never login in to system

I hope this helps

Hi,

Yes, the LastLoginDate attribute in Mendix does represent the last successful login time of the user, but there are a couple of important details to understand about how it works.

1. Does LastLoginDate indicate the user’s last login date?

Yes. The attribute LastLoginDate in the System.User entity is automatically updated by the Mendix runtime after a successful login. Each time the user logs in through the normal authentication flow (login page, SSO, etc.), Mendix updates this field with the current timestamp.

So it effectively stores the timestamp of the last successful authentication.

2. If LastLoginDate is blank, does it mean the user has never logged in?

In most cases, yes.

If LastLoginDate is empty (null) it usually means:

• The user account was created but the user has never logged in yet, or
• The login process did not go through the standard Mendix authentication mechanism.

There are a few scenarios where it might still be empty:

• The user was created via microflow or import but never logged in.
• The account was created by Administrator manually.
• The authentication mechanism does not trigger the standard Mendix login handler (for example some custom login implementations).

Additional note

LastLoginDate is maintained by the platform and should not be manually updated. If you need to track more detailed login history (for example every login event), the recommended approach is to create a custom LoginHistory entity and store entries during login events.

Summary

• LastLoginDate → timestamp of the last successful login
• Updated automatically by Mendix runtime
• If it is empty, the user has most likely never logged in yet.