The setup is that we have a Custom Object that is Parent to 16 different Child object types. When we "Submit for Approval" the process automatically locks the record (by default, per standard Salesforce approval process initial submission). 14 of the 16 child object types are locked as well and cannot have their records edited or have a new record created, but for some reason 2 of the objects are not blocked from record creation by the locking of the parent object.
This is strange for the lowest Users who do not have Modify All privileges on any of the child objects (which, according to the documentation, would allow them to circumvent the Record Lock). I've run several tests and examined security settings and object settings to find a difference between these two objects and the others, but I do not see anything that would allow this to happen. Any ideas why this would be possible?