≈ volna.computerSince February 2026
← My notes

Let a setting inherit again

A settings screen should show whether a value was chosen locally or inherited. Two projects can both display "Email notifications: on" and behave differently the next time an administrator changes the workspace default.

Consider a hypothetical issue tracker. A workspace enables email notifications for all projects. One project follows that default. Another has an explicit local choice to keep notifications on. When the administrator disables the workspace default, the first project should follow the change. The second should keep sending notifications. A toggle showing only the current value hides the decision that determines this behavior.

For this tracker, I would offer 3 choices: "Use workspace setting", "On", and "Off". Beside the inherited choice, the screen would show the current result: "Currently on, set by workspace". Choosing On would create a local override even while the workspace setting is already on. Choosing Use workspace setting would remove that override.

Storage needs to preserve the same distinction. Store an explicit off value as a local override, and preserve it when saving the form. Remove the override when the user chooses inheritance. A resolver can check for the presence of the override before consulting the workspace. Treating every false value as missing would silently enable notifications for a project whose owner turned them off.

Saving an unrelated setting can cause a subtler problem. Suppose the form loads the effective notification value, then sends every visible field back on save. Changing the project name could accidentally turn inherited notifications into an explicit choice. I would keep the notification mode in the form data and preserve it unless the user changes that field. The server also needs a defined operation for removing an override, since omitting a field from an update may mean "leave it alone".

To check this design, create 2 projects with notifications on: one inherited and one explicit. Rename both, then turn the workspace default off. Only the inherited project should follow. Finally, switch the explicit project to Use workspace setting and change the default again. That last step verifies that inheritance can be restored after a local choice.