Field | Explanation |
Age | Age in years (today - date of birth) |
Status | e.g. applicant, inactive, or active |
Created on | Date the database was created (by filling in the application form or by using the function ‘add new employee’) |
Last update | Date on which employee data was last changed (e.g. the planner changed their qualification, or the employee has a new address) |
Last login | Date on which they last logged into the web portal or mobile app (i.e. typed in username and password and clicked on ‘Login’). |
Last active | Date on which they were last active (e.g. changed their status or submitted work data) Please note: Since employees remain logged into the mobile app, the dates of their ‘last login’ and when they were ‘last active’ are not necessarily identical. |
Activated | Last time they were ‘activated’ (scenario A: employee was accepted as a candidate, scenario B: a planner added the employee, scenario C: the employee was set to inactive, then ‘reactivated’) |
Password expires | You can set a password expiry date by which employees are asked to renew their password. You can manually decide how frequently they are asked to do so. If you do not use this setting, their password never expires. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article