Active Directory to EHS Insight - Keep Safety in Sync

How does Active Directory to EHS Insight work?

We pull user accounts straight from your domain and our own framework maintains, orchestrates, and monitors the data integration. We pull only the attributes the integration needs: names, usernames, work emails, group memberships, and account status. On the EHS Insight side we use their RESTful API to keep users, departments, and your business hierarchy in step with your directory.

After data is pulled, we synchronize the two data systems following the rules your business needs. Once the integration is built, we monitor, fix issues as they happen, and ensure data reliably moves from Active Directory to EHS Insight.

Why does rapid user onboarding matter for your safety systems?

Compliance with regulatory standards is a real business risk. When you hire employees but your HR and IT processes can't keep up, the business encounters productivity slowdowns or an unnecessary compliance risk with new employees. Active Directory is the system of record for your employee's digital identity, and if every account already gets created there, it's the natural source of truth to automate user lifecycle management from. New employees need access to:

• Safety training assignments
• Incident reporting & review
• Compliance reporting

When the roster stops matching who actually works for you, all three break:

• New hires don't appear, so their required training never gets assigned. Nobody notices until an audit finds noncompliance.
• Employees disabled in Active Directory linger with open training assignments, dragging completion rates down.
• Supervisor changes in Active Directory don't reach the safety system, so incident follow-ups land with the wrong person, or nobody at all.

AutoIDM can automate your data entry from Active Directory to EHS Insight. This integration makes your directory the single source of truth for who's in the safety system:

• Users: created when an account is created in Active Directory, updated when its details change, and disabled when the account is disabled. When someone is disabled in Active Directory, their EHS Insight access is deactivated too.
• Supervisors: the reporting line from Active Directory is resolved to the right EHS Insight user, so incident workflows route correctly.
• Departments and hierarchy: your org structure syncs as both the department list and the business hierarchy that scopes permissions and reporting. When a department is renamed or retired in the directory, EHS Insight follows.
• Sign-in: users are set up for SSO, so employees use the company account they already have.

What about getting everyone on the same page in HR and IT? What's the project plan look like?

Getting the left hand to know what the right hand is doing in business is complicated. At AutoIDM, we have established a proven process to make sure everyone in your business is on the same page. The Active Directory to EHS Insight (and our general integration process) is adjusted depending on your needs, but it follows these main points.

1. Initial Meeting - (30 min) Bring all stakeholders together to align on the timeline, expectations, and responsibilities.
2. Access - (30 min) Architect a secure solution that gives AutoIDM access to what we need while keeping your IT team in control.
3. Business Rules - (1 hour) Align Active Directory with EHS Insight, build the rule set, and define the testing plan.
4. Testing - (~2 hours) Iterate with your champion to validate the integration and resolve issues quickly.
5. Deployment - Final deploy and full support for any adjustments or changes. Active Directory to EHS Insight is now up and running.

Business rules is where the edge cases get settled. What happens when a former employee comes back as a contractor and still needs their training history? Which accounts should the automation never touch? We'll capture those decisions in writing so HR, IT, and your EHS team are working from the same playbook.

Pull data from Active Directory: A simple approach is PowerShell. Review the ActiveDirectory PowerShell module documentation. Cmdlets like Get-ADUser let you pull user accounts and their attributes. Once you have data from Active Directory, you need to get it into EHS Insight.

Match up accounts: Once you've got employee data from Active Directory, you'll need to match it up to EHS Insight users. This can be done by tracking an external ID or fuzzy matching on name or email address. Store an external ID on the EHS Insight user so the link survives name and email changes.

Map data and push to EHS Insight: EHS Insight exposes a RESTful API with OpenAPI documentation, available through their support and developer program. Note that users, departments, and the business hierarchy are separate objects. Departments need to exist before you can reference them from users, and record updates require you to maintain all field values. You'll need to figure out record lifecycles: what happens when employees join, leave, change supervisors, etc.

Operationalize: After you've got the logic figured out, you'll want to set up monitoring to catch errors, alerting to let your team know when something requires their time, and training for the technicians who will be responsible for the automation. You'll also want to educate your IT and safety teams about what to expect and how to get support.