Hola Emma,
Check the affected user object and the OU, because enabling inheritance on the OU won't restore it for a user whose own inheritance is disabled. In Active Directory Users and Computers, select View > Advanced Features, then open the affected user's Properties > Security > Advanced. If Enable inheritance is displayed, inheritance is currently disabled. For an ordinary, nonprotected account, select it and Apply, then confirm that the expected entries appear with an "Inherited from" source.
If inheritance is already enabled, check the parent OU for the missing permission under Properties > Security > Advanced. Its "Applies to" scope must include the relevant user objects; an entry scoped to "This object only" won't reach newly created users. Microsoft explains object-specific inheritance here.
I'd avoid changing AdminSDHolder as suggested in the automated answer. It's the permissions template for protected accounts across the domain, so changing it can affect privileged-account security well beyond this OU. If inheritance becomes disabled again, check whether the user belongs directly or through nested groups to a protected group, such as Domain Admins or Account Operators.
Which specific permission is missing, and does the affected user's Advanced Security window show "Enable inheritance" or "Disable inheritance"? That will help distinguish blocked inheritance from an incorrectly scoped delegation.
Thanks,
James