Step 2 - Configuring your OneAdvanced Identity Organisation (Federated)

alethea.barlow@oneadvanced.com Updated by alethea.barlow@oneadvanced.com

Configuring your OneAdvanced Identity Organisation 

Before enabling OneAdvanced Identity in Time and Attendance you must ensure that you have configured your organisation within OneAdvanced Identity to reflect how you would like your employees and managers to login to the Time and Attendance web/mobile app.

Please note for federated users we recommend that you set the first login flow to 'automatic pairing - do not create user' against the provider tab, additional information can be found here.

Configuring your API Client

Time & Attendance synchronises users via APIs to Identity. By creating the API client, you will generate the Client ID and Client Secret that Time & Attendance needs to authenticate with the Identity APIs. To create your API Client ID and Client Secret, please follow the instructions detailed here. Once generated, this information should be entered into the Time & Attendance Identity onboarding screen as detailed in Step 3. 

    • Name (recommend “Time & Attendance”)
    • Type (set to confidential)
    • Grant types (set to client credentials)
    • Roles (set to User admin)
    • Redirect URLs (not required - use client credentials only and ignore authorization code)
    • Owner email (customer contact details)

Was this article useful?

Step 1 - Requesting your OneAdvanced Identity Service (Federated)

Step 2a - Setting up Federated using Entra, Google Identity or similar

Contact