Opening a teammate's timesheet used to show it read-only. You could see that somebody had logged 28 hours on a Tuesday because they forgot to stop a timer, and you could do nothing about it except ask them to fix it themselves.
Managers, administrators and owners can now edit those entries directly: change the hours, move time to the right project, correct the notes, add an entry somebody missed.
Every change is recorded
Editing your own timesheet is the ordinary business of the day and is not logged. Editing somebody else's is, every time, with who made the change, whose time it was, and what moved — "8:00 became 7:30" rather than just "something changed".
That is the part worth knowing about. The screen being read-only was never really the protection it looked like — the underlying API has always allowed a manager to do this, so it could already happen without leaving a trace. Now it leaves one.
What has not changed
Approved and invoiced entries stay locked for everybody, and moving an entry into or out of a submitted week is still refused.
Timers are still yours alone. You can record how long something took on a teammate's behalf, but you cannot set a clock running in their name — they would be left with a timer they never started. Submitting a week for approval is still theirs too; that is an assertion about their own work.
Who can do this follows the same rule as approvals: a manager sees the people they approve for, and administrators and owners see everybody.
Jumping to a date
The date on the timesheet is now the control that changes it. Select it to pick a day from a calendar instead of stepping the ‹ › arrows one day at a time — which was fine for yesterday and useless for last month.