Skip to content
SkyRosterBook a discovery call

Platform · Integrations

Connect rostering to the systems you use.

Share identity, attendance and scheduling information through supported integrations. Define the systems, data mappings and acceptance checks for your environment.

Inbound connections

Connect sign-in and employee provisioning.

Single sign-on

Let staff sign in with their organisational credentials. Standard SSO is included in Core, using Keycloak with Microsoft Entra ID over OIDC or on-premises Active Directory over LDAP. Kerberos is optional.

Directory synchronisation

A scheduled LDAP connection creates employee records and updates job numbers. It does not synchronise later name or email changes or deactivate staff who leave. Include SkyRoster account updates and offboarding in your administration process.

Import attendance and duty requests.

Access-control devices

Bring device clock events into attendance as approved entries. Each device can catch up after an outage, and manual corrections are retained. Attendance rules govern subsequent review.

Travel management

A scoped connector can create, update or cancel duty requests from travel-system events. Trips are split into daily segments around the employee’s schedule, with conflicts excluded. The applicable duty workflow then applies.

Outbound connections

Share payroll, calendar and notification data.

Payroll export

Export attendance, overtime, absence and allowance data in an agreed layout. Confirm the payroll target and reconciliation process; a different format or interface may require development. See payroll export.

Microsoft 365 calendar

Synchronise published shifts to Outlook calendars using an organisation-wide Azure app registration configured by IT. This integration supports a single tenant; other calendar providers are not standard connections.

Email and notifications

Send supported event notifications through email, push and the in-app notification centre. Localised text and category preferences control how staff receive updates.

Agree the scope for each integration.

Biometric, travel and payroll connectors are scoped for the customer environment. Your written offer identifies supported systems and versions, modules, setup, data mappings, testing and custom work.

Customer-specific code outside the supported shared release is assessed separately, including any dedicated-hosting requirement. See deployment options and pricing.

Discuss your integration requirements.

Start with a 20-minute discovery call about the identity, attendance and payroll systems you need to connect. We’ll then arrange a demonstration tailored to your priorities.