Skip to content

INTEGRATIONS

Connect the systems your workflow needs.

Connect enterprise hiring workflows to the HR systems you already run, including Workday, Oracle, SAP and UKG, plus calendars and Microsoft 365. Confirm what each connection reads or writes, who owns it, and which permissions it needs before rollout.

HR SYSTEMS

Works with the HR systems you already run.

Your HR system, connected

Roles, candidates and decisions sync with the HR system you already use. Microsoft 365 handles interviews, reminders and approvals.

Security

01

Workday

Connect Workday Recruiting for roles, candidate records and status updates.

02

Oracle and SAP

Connect Oracle and SAP SuccessFactors for roles, candidates and hiring status.

03

UKG and more

Connect UKG, Darwinbox and other HR systems through supported connections.

PERMISSIONS

Every connection has an owner and a limit.

01

Map the systems

List the systems each workflow needs and what it reads and writes.

02

Grant access

Limit sign-in and permissions to what each connection needs.

03

Test each handoff

Check data, errors and approvals before going live.

ROLLOUT

Prove one connection before adding more.

01

Map

Start with one repeatable workflow and the systems it touches.

02

Test

Check supported actions, data and failure handling with your technical team.

03

Operate

Name owners for exceptions, access reviews and changes.

Explore the platform.

See the workflows these connections support, how data is protected and our Microsoft partnership.

FAQ

Integration questions

What to know about setup, rollout and who makes the decisions.
Which HR systems are supported?
Workday, Oracle, SAP SuccessFactors, UKG and Darwinbox, among others. Confirm the connection for your setup during the demo.
Does Exterview AI replace our HR system?
No. Exterview AI works with your HR system and records every hiring action and approval.
Which Microsoft tools connect?
Teams, Outlook and calendars, through supported connections. See the Microsoft partnership page for details.
Who controls access?
Your team. Each connection uses only the permissions you grant.
What happens if a connection fails?
The failure is flagged to a named owner. Agree how failures are handled during setup.
Where can our security team review details?
See Platform security and the Trust Center, then walk through your review with our team.
What happens when an input or approval is missing?
An unresolved input or approval must not be treated as permission. Agree the blocked-work procedure and demonstrate its behavior for the configured workflow.
How do we validate human decision gates?
Test a representative progression and offer scenario. Confirm which authorized person reviews the evidence and how the approval is required before the next action.
Can an operator intervene during execution?
Assign an operator to review progress and handle exceptions. Confirm the intervention controls available for the workflow; do not assume rollback or unrestricted undo.
Who owns candidate progression and offer approvals?
Authorised people in your organisation own candidate progression, offer approvals and final hiring decisions. Smaya runs the approved work within those limits.
Does human oversight alone establish legal compliance?
No. Your team must assess its use, policies and the requirements that apply to it. Human decision ownership is a design limit, not a compliance certificate.
Where can we review security and data requirements?
Start with the Trust Center, then confirm access, processing, retention and deletion requirements with our team before sharing candidate data.