It turned out that the time reference in work logging is the local device system settings, not the cloud server-side.
This affects the configuration and can lead to data integrity issues as demonstrated below:
users are not allowed to log time retrospectively in the app configuration
a user can change their local time settings (back date), log the time, then change back their local time settings.
this allows users to bypass the configuration parameter
Suggested solution:
Setting the date/time based on the Cloud server’s time will allow to have a single time reference for all activities in the app, and the time displayed to the users will depend on their time zone settings and preferences.
Guest
| Tempo Products | Timesheet Reports & Gadgets (formerly Prime) |
| Tempo Platform | Cloud |
