Time tracking: user guide + developer guide (discussion #72) Time-Tracking recording time, the two switches and why the second one matters, per company, and what people will actually notice Time-Tracking-Developer-Guide why Tickets settings rather than System (every surface is a ticket surface), the new per-company settings layer and why it was worth building when the ACL table on #76 was not, why two switches, why per company is unusually clean here, the three enforcement points, and how to add the next setting Includes the trap this feature fell into twice in one day: a settings screen that renders a boolean BEFORE it knows the answer, so a failed load is indistinguishable from "off" — fixed on the Authentication page in the morning, reproduced on this tab in the evening by the person who wrote the warning. Sidebar entry under Tickets, beside Collision detection.