Before FormRH: 3 email exchanges per hire, manual AD account creation, and sometimes wrong permissions on day one. Today: HR fills one form, everything else runs automatically.
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: forgotten permissions, wrong access rights, accounts not ready on day one.
I designed FormRH to replace this coordination with a structured workflow. HR fills a form, the manager is automatically notified (with daily reminders if they don't respond), and the admin creates the AD account in one click — the worker calculates the correct groups based on job type and department, creates the LDAP account in the right OU, and generates a credentials file. Nothing can be forgotten.
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
> Sélectionnez un preset et cliquez sur "▶ Run" pour lancer la simulation
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