Home · See it running

Systems Admin

A real lockout: one agent blocked from its own files, then found, fixed and tested

A real lockout from 28 September 2026. The Communications Manager added a safety check meant to keep it inside its own folder, but the settings it copied still named another agent's folder, so every file it tried to save was refused. The Systems Admin found the wrong folder name, fixed it, tested it and reported back.

Systems Admin: what happens in the video1An agent adds a safety checkIt's meant to keep each agent inside itsown folder.2The check guards the wrongfolderEvery file the Communications Managertries to save is refused.3It can't fix itselfChanging its settings is blocked too, sothe Owner asks the Systems Admin.4Finding the causeThe settings still name the ExternalAuditor's folder.5The fixTwo quick text replacements changednothing; editing the settings properlyworked.6Testing itSaving in its own folder works; savinganywhere else is still refused.7Reporting backThe fix is saved, and the studio's setupnow fills in each agent's own folder.