Currently, if a team account enables Block Inheritance on categories or articles, the system blocks deletion of that user until the restriction is manually removed by the same account. While this behavior is expected from a security standpoint, it creates a deadlock when the user who applied the block inheritance has left the organization and no admin has access to that account.

In such cases, there is no admin-level override or recovery mechanism to remove the block inheritance, resulting in inactive team accounts that cannot be deleted without backend intervention.

Introducing a controlled admin-level override to view and remove block inheritance applied by inactive users would prevent these deadlock scenarios