Network Access Request Management System

Overview

NARF Form Handler is a custom WordPress plugin used by Ontario court organizations to process network access requests and track employee profiles and access changes. I built the conditional request form, server-verified review and submission workflow, dedicated database layer, and administrative tools for judicial managers.

What I Built

• I implemented request flows for new users, staff transfers, access changes, account enable/disable, and staff deletion, with cascading organization selections, role templates, address suggestions, and organization-specific access checklists.
• I built the Request details -> Review -> Complete workflow, including Microsoft 365 MSAL-based submitter auto-fill, server-side identity verification, administrator-managed submission eligibility, and retry-safe persistence.
• I modeled employee users, organization-bound profiles, and current access separately from historical requests, with lifecycle transitions and tracked edits to active profiles.
• I built the Submissions, Users, and Settings admin modules, including searchable records, profile detail and editing, access catalogs, role and division templates, and submission whitelist management.
• I implemented configurable email notifications and formatted templates, optional PDF attachments, protected requester PDF downloads, CSV export, and administrator print/save-as-PDF views.

How It Works

• Managers choose the staff change they need and fill out a guided form. Role templates suggest the access an employee needs, so managers do not have to remember individual distribution lists, security groups, or mailboxes.
• Managers review and submit their request, then download a PDF for their records. The plugin saves the request and emails the service desk, where staff assign the ticket to IT support technicians.
• Administrators use the WordPress dashboard to look up requests and employee records, update templates, and change notification recipients and other settings without editing code.

Technical Highlights

• Role-based access templates: I captured common access requirements in reusable templates, giving experienced and newly appointed managers a starting point without needing to know the technical setup.
• Settings the team can maintain: I put everyday configuration in the admin dashboard so the product can adapt to staff and process changes without depending on me to update the code.
• Checks that protect the records: I added server-side permission checks and duplicate-submission protection, and kept original requests separate from editable employee profiles so later changes do not overwrite request history.