This indicates the storage type of the conceptual row for a policy-to-resource-user/group application entry, where nonVolatile preserves that specific application, which policy is applied to which consumer, across a reload. Losing this to volatile storage means the policy-application link itself would need to be redone after a reload even if both the policy definition and the resource group/user still exist independently. An admin who correctly set the policy definition itself to nonVolatile but left this application-table row volatile would find, after a reload, that the policy still exists but is no longer actually applied to the process it was attached to.