Marshalls Admin

<p>An online admissions system is only as good as the tool the staff use to run it:</p><ul><li><strong>One shared key was not enough.</strong> The admin API needed each administrator to sign in as themselves, so every change could be traced.</li><li><strong>Applicants' documents are private,</strong> and so is the information in an application, so the tool needed strong access control.</li><li><strong>Content changed by hand</strong> meant waiting on a developer for every programme, fee or intake.</li><li><strong>Staff step away from their desks,</strong> but typing a long password again and again slows the work down.</li><li><strong>Updates had to reach every installed copy</strong> without anyone visiting each computer.</li></ul>

<p>We built Marshalls Admin as a <strong>focused desktop console</strong> in the school's gold and black:</p><ul><li><span style="color: #a16207"><strong>Per-administrator sign-in</strong></span> replaced the shared key, with a password reset by a code emailed to the administrator.</li><li><strong>A quick PIN</strong> for fast sign-in. It is checked by the website, not on the computer, and the app <strong>locks after an hour idle</strong>, but never while someone is using it.</li><li><strong>Admissions tools:</strong> programmes and intakes (the website trusts these lists), applicants, applications with their private documents, payments and enquiries.</li><li><strong>Site settings:</strong> the public pages' text, images, contact details and branding are edited here and appear on the website.</li><li><strong>Encrypted backups,</strong> a notifications feed, an audit trail and error logs.</li><li><strong>Self-installing updates:</strong> signed installers are built automatically, and the app checks for a new version every 30 minutes and installs it without interrupting unsaved work. Photos are shrunk before upload.</li></ul>