A dedicated repair mode that allows admins to gain access when the system cannot be reached normally

Admins want a safe, restricted repair mode that remains accessible even when normal login is broken, so they can fix critical configuration issues without requiring direct database or file system access. Problem / Pain: When a critical configuration error occurs, such as incompatible apps, broken permission conditions, or faulty hooks, it can make normal login impossible. In these situations, admins have no way to access the system to fix the problem through the interface and may be forced to intervene directly at the database or file system level. This is risky, time-consuming, and requires technical expertise that not all admins have. Impact / Benefit: A dedicated repair mode that bypasses normal session logic and grants restricted administrative access would give admins a reliable recovery path when the system cannot be reached through normal login. Critical issues could be resolved through the interface without risky manual interventions, reducing downtime and the risk of compounding the original problem. Example use case: An admin installs a new app that introduces a faulty session hook, making login impossible for all users including themselves. With a repair mode, the admin could log in through a separate, hook-independent path, access the administration area, deactivate the problematic app, and restore normal access without touching the database or file system. Idea source: Internal suggestion Voting note: Vote for this idea if this need is relevant to you as well.