Control whether people can keep working in Clippter when they have open (unlogged) contract days, and how logging behaves when a project’s hour budget is nearly full.
These settings live under Settings → Workspace time rules. Only owners and managers with the right permissions can change them.
Before you start
- Team members need a work contract (hours and tracking expectations) so Clippter knows which days count as open work days.
- Holidays and absence reduce what counts as a day that must be logged.
- Contract exceptions on Team → a person can change who is affected.
Open-day lock (enforce workspace time rules)
Turn rules on or off
- Go to Settings → Workspace time rules.
- Under Enforce workspace time rules, choose Yes or No.
- Save.
No: no app lock from open days. People can use Clippter even if time is missing.
Yes: Clippter can lock the app when either threshold below is met. The bell / reminders and the lock use the same open-day total.
Block after open days (total)
When rules are on, set how many open contract days without time logged are allowed before lock.
Default example in the product: 5. So with that value, after five open days the person is locked until they catch up (or skip where the product allows).
Range: 1-31 days.
Block if oldest open day is at least (days ago)
Separately, lock if the oldest open day is too far in the past, even when the total count is still low.
Default example in the product: 14. So one forgotten day from two weeks ago can lock someone even if they only have a few open days in total.
Range: 1-90 days.
Either threshold can trigger the lock. The lock message says which rule fired.
What “open days” means
Roughly: contract work days where Clippter expects time and none (or not enough) was logged. Holidays and approved absence don’t count the same as a normal missing day. Exact behaviour depends on the person’s contract and the workspace holiday calendar.
Project hour budget caps
This section is separate from the open-day lock. It applies when logging time against a project that has an hour budget.
- On the same Workspace time rules page, open Project hour budget caps.
- Choose a mode, then Save.
| Mode | What happens |
|---|---|
| Off | No budget gate when logging. |
| Soft (confirm) | Near or over budget, Clippter warns. Over budget, the person must confirm to log anyway. |
| Hard (block) | Over budget logging is blocked. |
Warn at (% of budget)
When Soft or Hard is on, set the percentage where the early warning appears (for example 85%). Soft confirm and hard block at full budget still use 100%.
Range: 50-100%. Default: 85%.
What people experience
- With open-day rules on and a threshold hit: they see a lock / gate until they log the open days (or use skip where offered).
- Soft hour cap: warning near the percentage; confirm when going over budget.
- Hard hour cap: can’t log past the project budget.
Managers can review targets under Settings → Team tracking overview (linked from the time rules page).
Common mistakes
- Turning rules on without contracts set: unclear who should log what.
- Setting “block after open days” very low (for example 1) without telling the team: people feel randomly locked out. See Why am I locked out of the app?.
- Confusing hour caps with open-day lock: hour caps are per project budget; open-day lock is about missing personal time.
- Expecting holidays alone to fix vacation: holidays mark non-working days; vacation balance still comes from the work contract.