Before FormRH: 3 to 5 email exchanges per hire, manual Active Directory account creation with groups assigned from memory, and no tracking of post-creation tasks. Today: HR fills one form — the full workflow runs through to an active AD account. And all assignment rules (groups, OU, N2F) are editable from an admin interface without touching the code.
Every hire at ESLC triggered a manual chain: HR emailed the new employee's info to the manager, the manager replied with equipment needs, and IT manually created the Active Directory account — assigning groups from memory. Result: 3 to 5 emails per hire, wrong permissions on day one, and no tracking of post-creation tasks.
FormRH automates the entire process, onboarding and offboarding. On the way in: an HR form triggers the full workflow through to AD account creation. On the way out: a dedicated page records the end date so IT can deactivate the account. And since the admin overhaul, all AD group assignment rules, OU paths, companies, and N2F configurations are editable from a web interface — no developer, no redeployment.
FormRH structures the workflow around 4 roles. Each actor sees only what concerns them — HR doesn't see AD administration, managers only see their own employees.
First name, last name, job type, department, city, start date, assigned manager
Laptop/desktop, badge, phone, software (Icopitole, Sage, N2F…), free notes
Select eligible employees + click "Create AD accounts"
Check off software and hardware installations in the /histo log
Triggered from the history record if N2F was checked in the manager form
The Next.js frontend relies on a dedicated Express backend that orchestrates 4 independent integrations: Active Directory LDAP for account creation, Microsoft Graph API for authentication and manager lookup, the N2F API for expense accounts, and SMTP Exchange for automatic emails.
> Sélectionnez un preset et cliquez sur "▶ Run" pour lancer la simulation
Before FormRH
After FormRH
Notification emails
At every workflow step, the right email goes out automatically — no need to remember to notify the manager or IT
Daily reminders
If the manager hasn't completed the form, they receive a daily reminder email (cron job) until they do
AD creation in 1 click
The worker creates the account in the correct LDAP OU, assigns AD groups based on job/department rules, and generates a credentials file
N2F account
Automatic creation via the N2F API with name normalization and manager email fetched from Azure AD
Config without redeployment
8 admin tabs in MongoDB: new AD rules, new departments, new cities — without touching the code
Confidential application — restricted access
For confidentiality and legal reasons, I cannot share access to this application. It is deployed in production on ESLC's internal network and contains sensitive HR data.