What happened

A customer tried to turn off “Manual Clocking” but kept seeing it switch back on.

The root cause wasn’t a bug—it was the way our settings inheritance works:

Two layers of settings:

Global – applies everywhere by default.

Location-level – each location can override any Global setting

Detaching on first change:

As soon as an admin changes a setting inside one location, that setting stops inheriting the Global value for that location only.

The confusion:

The customer toggled Manual Clocking inside a single location, unaware they’d overridden only that site.

Global still had Manual Clocking ON, so other locations—and the Global view—continued to show ON, making it look like the setting “didn’t save.”

Pain points