Record lock

The Lifecycle

Transitions Explained

Protection is stored independently on the product, setup and kind tax default. It supplements permissions: deletion-only protection leaves editing available, while combined protection also blocks updates. The cited milestone confirms product lock behavior. A product or setup editor can explicitly reduce combined protection during replacement; defaults use different release checks.

What Cannot Happen

Omitting protection does not request an unlock. Combined product or setup protection must be explicitly reduced for replacement to proceed. A combined lock on a kind default prevents replacement even when the request tries to clear it. A setup's deletion lock also blocks deleting its product.

Concurrency and Timing

Product and setup protection changes use their common product lock and their own record versions. Kind-default changes use the default row and version independently.