Integrating Engage with Other Business Systems

• An existing integration may still require configuration, data mapping, testing and coordination with the other provider.
• Not every field or workflow is automatically included.
• Security, privacy, access and source-of-truth responsibilities must be agreed before information is transferred.
• Contact Engage Support to confirm whether an available connection is suitable for your organisation.

Engage has supported connections with:

• Intuto
• Tap into Safety
• SafeTrac

Intuto and Tap into Safety use API-based workflows for user creation, course availability and training results. SafeTrac supplies completion information to Engage through a nightly file.

Integrated courses are allocated in Engage using roles and locations so that comparable employees are treated consistently.

Read: Integrating Engage with Learning Management Systems

Engage supports inbound employee-data connections with:

• Datacom
• DataPay
• iPayroll
• PayHero
• BambooHR

For these connections, the employee is created in the payroll or HR platform. Engage receives the information, creates the employee profile and user, applies subsequent employee-data changes and processes termination dates received from the source system.

A customer-specific PayGlobal integration works in the opposite direction. Approved employee and termination information is sent from Engage to PayGlobal through SFTP for import.

Read: Synchronising Employees with Payroll and HR Systems

Engage supports identity and access options including:

• Microsoft work-account single sign-on
• Microsoft Entra ID user provisioning through SCIM
• Customer-specific SAML-based SSO arrangements
• Two-factor authentication for additional Engage login security

SAML, SSO and AD FS are related concepts rather than separate interchangeable products. The appropriate configuration depends on the organisation's identity environment and should be confirmed during implementation.

Read: Using Microsoft Single Sign-On (SSO)

Read: Setting Up Microsoft Entra ID User Provisioning with SCIM

Authorised customers can use the Engage outbound API to retrieve selected Engage information for approved reporting and integration purposes.

The currently documented endpoints use read-only GET requests and require Bearer Token authentication. The separate API documentation portal remains the technical source of truth for available endpoints and fields.

Read: Using the Engage Outbound API

When contacting Engage Support, provide:

• The systems that need to connect
• Which system should be the source of truth
• The information that must be transferred
• The required direction and frequency of updates
• How new employees, changes and terminations should be handled
• Any approval or security requirements
• The intended business outcome

Engage can then assess whether an existing connection is suitable or whether customer-specific development and implementation work may be required.

Does an integration eliminate all manual administration?
Not necessarily. The outcome depends on the information available from the source system, agreed mappings and the workflow being supported.

Can every existing integration be enabled for any customer?
No. Some integrations are broadly supported, while others were developed for a particular customer or workflow.

Are all integrations real-time?
No. Some use APIs, while others use scheduled files or customer-specific transfer processes.

Is two-factor authentication an external-system integration?
No. It is an additional Engage login-security measure, included here because it forms part of the wider identity and access options.