Effectively managing project and Employee hours is essential for avoiding overwork, controlling project costs, and ensuring payroll compliance. The Time Limits feature is designed to set Time Limits on task tracking, allowing Managers to set predefined thresholds so that Employees only work within their allocated time and do not exceed it.
Goals:
Limiting how much time each Employee can log on a project.
Setting a different limit for one specific Employee on one specific project.
Limiting one specific Employee’s total work time across all their projects.
Ability for Employees to be aware of the limits set, to know when the limit is reached and when they can start logging time again. We want to avoid abruptly stopping a task the moment the threshold is reached, as this could cause Employees to work for hours without realizing their time wasn’t logged.
The Time Limits feature allows teams to set structured boundaries for managing work effectively.
There are three kinds of Time Limits:
Project limit
Employee limit on a specific project
Employee limit across all projects
Each kind is explained below, followed by how they work together.
The Three Kinds of Time Limits
Project limit
Set for one project.
Applies to every Employee assigned to that project.
Each Employee’s time is counted separately. It is not a budget the team shares.
Example: a Project limit of 4 hours per day means each Employee on the project can log up to 4 hours a day on it.
Employee limit on a specific project
Set for one specific Employee on one specific project.
Applies only to that Employee, and only on that project.
Replaces the Project limit of the same cycle (daily, weekly or monthly) for that Employee, whether it is higher or lower.
Other Employees on the project keep the Project limit.
It does not apply to the Employee’s other projects. To give an Employee their own limit on several projects, set one for each project.
Employee limit across all projects
Set for one specific Employee, without choosing a project.
Counts all the work time that Employee logs, on all their projects and in manually added shifts, added together.
How the Limits Work Together
To find which limits apply to an Employee on a project:
For each cycle (daily, weekly, monthly):
If the Employee has an Employee limit on this specific project, that limit applies.
If not, the Project limit applies.
If the Employee has an Employee limit across all projects, it applies as well.
All the limits that apply count at the same time. Time logging stops as soon as one of them is reached:
Reaching a Project limit or an Employee limit on a specific project stops logging on that project only. The Employee can keep logging time on their other projects.
Reaching an Employee limit across all projects stops logging on every project.
Example:
Project A has a Project limit of 4 hours per day and 100 hours per month.
Anna has an Employee limit on Project A of 8 hours per day and 40 hours per week.
Anna also has an Employee limit across all projects of 6 hours per day.
On Project A, Anna’s limits are:
8 hours per day: her own limit on Project A replaces the Project’s 4 hours.
40 hours per week: her own limit on Project A (the project has no weekly limit).
100 hours per month: the Project limit, because she has no monthly limit of her own on Project A.
6 hours per day across all her projects: her Employee limit across all projects. It is reached first, so on any day she stops after 6 hours in total, on Project A and her other projects together.
Other Employees on Project A keep the Project limits: 4 hours per day and 100 hours per month.
Setting Time Limits Include:
Daily Limits: Resets each day.
Weekly Limits: Resets each week.
Monthly Limits: Resets each month.
Each cycle includes settings for Start Date & Time and an optional Timezone.
If no timezone is specified, the system defaults to local Employee’s timezone to support the needs of global teams.
Each kind of limit can have one limit of each of these cycles: daily, weekly and monthly.
Once a limit is reached, the Employee cannot log more time until the cycle in which they reached it resets:
for a Project limit or an Employee limit on a specific project: on that project;
for an Employee limit across all projects: on all projects.
Configuration is set up through the API. To begin, the user should:
1. Visit the Insightful Developer Portal.
2. Open the Time limit section on the left sidebar.
This section contains all the necessary rules for configuring Time Limits. The IDs you send decide which kind of limit you set:
project ID only: Project limit;
employee ID and project ID: Employee limit on a specific project;
employee ID without a project ID: Employee limit across all projects.
Updating and Deleting Time Limits
Think of Time Limit as flexible limits on the amount of time you can log. You can set one daily, one weekly and one monthly Time Limit:
for a project;
for each Employee on a specific project;
for each Employee across all projects.
Each has its own start time and duration.
If you need to change a Time Limit, update the existing one with the Time limit - update request, including its cycle (daily, weekly or monthly). If a Time Limit with the new cycle already exists at the same level (for the project as a whole, or for the same Employee), the update is rejected with the error “Item already exists for the employee”, and neither limit changes. You can pull the list of all currently active limits.
To remove a Time Limit entirely, you can delete it from the list, and if you want you can delete limits in bulk. After deletion, you can log time without any restrictions for that project.
Updating Time Limit via API
If the EmployeeAPI is hit it updates the Insightful desktop app's Time Limit. Updating the Time Limit via the API will automatically propagate the new values to a user device. Any device within the scope of the updated time limit will receive the changes.
Time to sync
When Time Limit values are changed and updated they are typically applied to the device in real-time (within 5 minutes maximum), assuming the device has an active internet connection and the Insightful desktop application is running at the time.
Tracked data upload is synced in 2-minute sequences.
Please note that Employee users must be Clocked-in to receive the time limit updates. Failing to do that may cause misunderstandings of time limits set.
When the Time Limit is updated, one of the following scenarios may happen:
Users that are Clocked-in and have an internet connection should immediately receive the updated limit,
Users that are not Clocked-in but have an internet connection will receive the updated Time Limit as soon as they Clock-in. Clocking-in acts as a trigger for the Insightful desktop app to check for any updated Time Limits values.
Users without an internet connection will receive the updated limits as soon as they regain connectivity and the Insightful desktop app syncs the necessary data.
Force sync
Force sync can be triggered directly from the Insightful widget. When a user selects the Sync Now option, it functions as a force sync for all values, including updates to the Employee entity.
The Sync button is located in the bottom left corner of the Insightful widget.
Increasing Project Time Limits
If you increase a Project limit, check the Employees on that project:
An Employee who has an Employee limit on this specific project, for the same cycle, keeps that limit. The new Project limit does not apply to them.
An Employee whose Employee limit across all projects is lower still stops when they reach it.
Change those limits too if the Employee should get the new value.
Understanding Time Tracking Behavior
When a Time Limit is active, Employees need to know the set Time Limit and its timeframe, ensuring clarity on when limits will affect time tracking. If a Time Limit (such as daily or weekly limits) is in place, this closer, more immediate Time Limit should always be displayed to help Employees monitor their progress.
If an Employee has an Employee limit on a specific project, they see that limit instead of the Project limit.
If not, they see the Project limit.
Employees see every limit that currently applies to them, not only the one closest to being reached.
Once the Time Limit is reached, time tracking will automatically stop for that project, and Employees will receive an alert. Employees will encounter the following scenarios:
1. If the Time Limit has not been reached: Users will see the nearest Time Limit value, total Time Limit, and remaining time available for logging within the current Time Limit timeframe.
2. If the Time Limit is reached: Users will be notified of when the next Time Limit timeframe begins.
3. While the Time Limit is active: Employees are unable to initiate new time tracking.
Upon reaching a Time Limit, Employees will see the prompt: “You’ve logged 50 hours for this project. Time logging has been paused as you’ve reached your time logging limit.”
Each project with an active Time Limit for a specific user will display a tag, indicating the presence of time restrictions. When users hover over this tag, a tooltip appears with the message, “This project operates within a defined Time Limit.”
Users can easily view all active Time Limits that apply to them, with each limit clearly associated with its respective cycle. In the widget, each Time Limit appears as a countdown timer, enabling users to track their remaining time in real-time across all cycles.
When a Time Limit is reached, the user receives a notification indicating that the limit has been met. Within the widget, a red indicator will appear next to the cycle that has reached its limit. By hovering over the indicator, the user can see the exact time when the limit will reset.
For instance, for a daily limit, it may display: “Daily limit of 07:30h resets at 10:30 am.”
Time Limits Across Multiple Projects
When an Employee is assigned to multiple projects, each project’s limits count separately. An Employee limit across all projects, if set, can stop them earlier (see Case 2).
Example – Case 1 (no Employee limit across all projects):
An Employee is assigned to two projects:
Project 1: 5 hours per week
Project 2: 10 hours per week
The Employee can log:
Up to 5 hours on Project 1
Up to 10 hours on Project 2
This allows a total of 15 hours per week across both projects.
Employee Limit Across All Projects
An Employee limit across all projects counts the time logged on all projects together.
Example – Case 2 (Employee limit across all projects applied):
An Employee is assigned to two projects:
Project 1: 5 hours per week
Project 2: 10 hours per week
Employee limit across all projects: 9 hours per week
In this case:
The Employee can log up to 5 hours on Project 1
The Employee can log a maximum of 9 hours on Project 2, even though the Project limit is 10 hours
The Employee limit across all projects stops the Employee at 9 hours in total, even though the two Project limits add up to 15 hours. For example, after 5 hours on Project 1, they can log only 4 more hours on Project 2 that week.
Troubleshooting Common Issues
Issue:
The weekly cap shows 60 hours, even though the Project limit was increased to 80 hours.
Solution:
Check whether the Employee has either of these, set to 60 hours per week:
an Employee limit on this specific project: it replaces the Project limit for that Employee;
an Employee limit across all projects: it stops logging when it is reached.
Ask an Admin to raise or delete that limit. Once updated, the correct weekly cap will be displayed in the app.

