guide emory kronos login accessing essential steps

Step-by-Step Login Process for Kronos at Emory

Accessing Kronos via Web Browser

1. Navigate to the Kronos Login Page
   Open a web browser and enter the following URL in the address bar:

   https://emory.kronos.com/

   This is the official Emory Kronos login portal. For security, avoid using third-party links or bookmarks that may redirect to unauthorized sites. If you frequently access Kronos, bookmark this URL directly in your browser for convenience. Ensure the bookmark is stored in a secure location (e.g., a password manager or encrypted folder) to prevent unauthorized access.
2. Enter Emory NetID and Password
   On the login page, input your Emory NetID in the designated field. The NetID is typically formatted as:

   [first_initial][last_name]@emory.edu (e.g., jdoe@emory.edu)

   Follow this with your Emory password. If you are unsure of your credentials, retrieve them from the Emory NetID Lookup Tool or reset your password via Emory’s Password Management Portal.
3. Complete Multi-Factor Authentication (MFA)
   After entering your credentials, you will be prompted to verify your identity via MFA. Emory supports the following MFA methods:
   • Duo Mobile App (push notification or phone call)
   • SMS Text Message
   • Hardware Token (if assigned)
   Select your preferred method and follow the on-screen instructions. If you encounter issues with MFA, refer to the troubleshooting section below or contact the Emory IT Help Desk at (404) 727-4357.
4. Access the Kronos Dashboard
   Upon successful authentication, you will be redirected to the Kronos Workforce Central dashboard. This interface provides access to timecards, schedules, benefits, and other HR-related tools. Familiarize yourself with the layout, as navigation varies slightly based on your role (e.g., employee, supervisor, or manager).

Accessing Kronos via Mobile App

1. Download the Kronos Mobile App
   Search for and install the official Kronos Workforce Central app from:
   • Apple App Store: Kronos Mobile
   • Google Play Store: Kronos Mobile
   Avoid third-party app stores or unofficial versions, which may pose security risks.
2. Configure the App with Emory’s Login Credentials
   Open the app and select "Add a Company". Enter the following details:

   Company URL: emory.kronos.com

   Proceed to log in using your Emory NetID and password, followed by MFA verification as outlined in the web browser steps. If prompted, enable push notifications for timecard deadlines or approval requests.
3. Navigate the Mobile Dashboard
   The app’s interface mirrors the web version but is optimized for touch. Key features include:
   • Timecard submission and approval
   • Schedule viewing and updates (for eligible roles)
   • PTO request submission
   • Payroll and benefits information
   Customize app settings to receive alerts for timecard deadlines or manager approvals.

Required Credentials and Retrieval Methods

1. Emory NetID
   The NetID is your primary identifier for Emory systems, including Kronos. It is typically assigned during onboarding and follows the format:

   [first_initial][last_name]@emory.edu (e.g., ajsmith@emory.edu)

   Retrieval Methods:
   • Use the Emory NetID Lookup Tool if you know your Emory ID number.
   • Contact the Emory IT Help Desk at (404) 727-4357 or submit a ticket via Emory IT Support.
   • For new hires, check the onboarding email from Emory HR for your NetID assignment.
2. Emory Password
   Your Emory password must comply with university security policies (e.g., minimum 12 characters, including uppercase, lowercase, numbers, and symbols). If forgotten, reset it via:

   Emory Password Management Portal

   Ensure your password is unique and not reused across other accounts to mitigate security risks.
3. Multi-Factor Authentication (MFA) Setup
   MFA is mandatory for Kronos access. If you have not enrolled in MFA, complete the setup via:

   Emory Duo Security Portal

   Supported MFA Methods:
   • Duo Mobile App (recommended): Install the app on your smartphone and link it to your Emory account.
   • SMS Text Messages: Requires a mobile number registered with Emory IT.
   • Hardware Token: Assigned to employees with specific security requirements.
   Troubleshooting MFA Issues:
   • Ensure your device has an active internet connection (for Duo Mobile).
   • Check for app updates or reinstall the Duo Mobile app if notifications fail.
   • Verify your phone number or email in the Duo portal if SMS/email methods are selected.

Troubleshooting Common Login Errors

1. "Invalid Credentials" Error
   This message appears when the NetID or password is incorrect, expired, or locked due to multiple failed attempts.
   Resolution Steps:
   • Verify the NetID format (e.g.,

     ajsmith@emory.edu

     ), ensuring no typos or extra spaces.
   • Reset your Emory password via the Password Management Portal.
   • If the account is locked, contact the Emory IT Help Desk to unlock it. Provide your Emory ID number for verification.
   • Check for caps lock or keyboard layout issues, especially on mobile devices.
   Visual Cue: A red error banner at the top of the login page with the text:

   "Invalid username or password. Please try again

   Security Protocols and Multi-Factor Authentication (MFA) for Emory Kronos Access

   Emory University enforces Multi-Factor Authentication (MFA) for Kronos login to mitigate unauthorized access risks and align with institutional cybersecurity standards. MFA adds an additional verification layer beyond passwords, requiring users to confirm identity via a secondary device or method. This section outlines the mandatory MFA methods (Duo Security and Emory Mobile Auth), their setup procedures, and best practices to ensure secure access while minimizing disruptions.
   

   Mandatory MFA Methods for Kronos Login

   Emory supports two primary MFA methods for Kronos access:
   1. Duo Security – A widely adopted third-party authentication platform integrated with Emory’s systems.
   2. Emory Mobile Auth – A university-managed mobile application offering seamless authentication without third-party dependencies.

   Setup Process for Duo Security
   To enroll in Duo for Kronos:
   1. Navigate to the Emory Duo Enrollment Portal (https://duo.emory.edu) using a personal device (not shared).
   2. Select "Enroll Your Device" and choose "I have a phone" or "I have a tablet" (mobile push is recommended for ease).
   3. Install the Duo Mobile app (iOS/Android) or use a landline phone if mobile access is unavailable.
   4. Enter a verification code sent to your enrolled device to complete enrollment.
   5. Configure backup methods (e.g., SMS passcodes or hardware tokens) in case primary devices are unavailable.

   Setup Process for Emory Mobile Auth
   For Emory Mobile Auth:
   1. Download the Emory Mobile Auth app from the Apple App Store or Google Play Store.
   2. Open the app and sign in using Emory NetID credentials.
   3. Enable push notifications for instant approvals or configure one-time passcodes as a fallback.
   4. Verify enrollment by completing a test login via the app.
   

   Comparison of MFA Methods: Ease of Use, Security, and Recovery Options

   The following table evaluates the two MFA methods based on user convenience, security robustness, and recovery mechanisms:
   

   Criteria	Duo Security	Emory Mobile Auth
   Ease of Use	Mobile push notifications require app installation but offer one-tap approvals. SMS/phone call options available for users without smartphones. Hardware tokens (e.g., YubiKey) supported for advanced security.	Seamless integration with Emory’s existing systems; no third-party app required beyond Emory Mobile Auth. Push notifications and passcodes available in a single app. Supports biometric authentication (Face ID/Touch ID) for added convenience.
   Security Strength	End-to-end encrypted push notifications; resistant to phishing. Hardware tokens provide phishing-resistant authentication. Session monitoring detects suspicious logins.	University-managed app with Emory’s security protocols (e.g., encryption, tokenization). Biometric verification reduces reliance on passwords. Centralized IT support for troubleshooting.
   Recovery Options	Backup methods: SMS, phone call, or hardware tokens. Self-service recovery via Duo Admin Portal (with NetID verification). IT support required for account lockouts beyond 3 failed attempts.	Passcode fallback if mobile device is unavailable. In-app troubleshooting guides and direct IT contact via the app. No third-party dependency reduces recovery complexity.

   Consequences of Failed Login Attempts and Mitigation Strategies

   Kronos enforces account lockout policies to prevent brute-force attacks:
   

   After 3 failed attempts, access is temporarily suspended for 15 minutes.

   After 5 failed attempts, the account is locked for 1 hour, requiring IT intervention for recovery.

   Repeated lockouts may trigger a permanent suspension and escalation to Emory’s Information Security Office (ISO).

   Avoiding Lockouts
   

   Use remembered credentials (e.g., password managers) to reduce manual entry errors.

   Enable session timeouts to prevent unauthorized access if a device is left unattended.

   Test MFA enrollment during non-critical hours to familiarize yourself with the process.

   If locked out, contact Emory IT Service Desk (https://it.emory.edu/support) with your NetID and emergency contact details for verification.

   Best Practices for Securing Kronos Credentials

   Protecting Kronos access requires proactive measures against credential theft and phishing. Implement the following safeguards:

   - Password Management
   

   Store credentials in a reputable password manager (e.g., 1Password, Bitwarden) with master password encryption.

   Avoid reusing passwords across personal and institutional accounts.

   - Device Security
   

   Enable device encryption (BitLocker/FileVault) and biometric locks (Face ID/Fingerprint) on all devices used for MFA.

   Keep operating systems and apps updated to patch vulnerabilities.

   - Phishing Awareness
   

   Verify Kronos login URLs (must start with `https://kronos.emory.edu` or `https://workday.emory.edu`).

   Ignore emails requesting password or MFA code submissions—Emory IT never asks for these via unsolicited messages.

   Critical Warning: Phishing attacks targeting Kronos credentials often mimic legitimate login pages with slight URL variations (e.g., `kronos-verify.emory.edu`). Always navigate to Kronos via the official Emory portal (https://intranet.emory.edu) or a bookmarked link. Report suspicious emails to phishing@emory.edu.

   MFA Device Maintenance

   Regularly update the Duo Mobile or Emory Mobile Auth app.

   Remove compromised or lost devices from MFA enrollment immediately via the respective portals.

   Test backup authentication methods periodically to ensure functionality.

   Troubleshooting Login Issues and Technical Support for Emory Kronos Access

   Accessing Emory Kronos requires seamless integration with Emory’s identity management systems, including NetID authentication. Despite robust security measures, users may encounter login failures due to technical errors, credential issues, or system outages. This section provides structured guidance to diagnose and resolve common login problems, along with official support channels and procedural steps to recover access without data loss.
   

   Official Emory IT Support Channels for Kronos Login Issues

   Emory University maintains dedicated support channels for Kronos-related technical difficulties. Users experiencing login failures should prioritize the following official resources, which include response time expectations based on service-level agreements (SLAs):
   

   • Emory IT Service Desk (Primary Support)
     • Phone: +1 (404) 727-7777 (available 24/7 for critical issues). Standard business hours (8:30 AM–5:00 PM ET) may experience shorter wait times.
     • Email: it.service.desk@emory.edu (response within 24 hours for non-urgent issues; escalations may be prioritized for Kronos outages).
     • Live Chat: Available via the Emory IT Support Portal (response typically within 1–5 minutes during business hours).

     Note: For system-wide Kronos outages (e.g., scheduled maintenance or failures), Emory IT publishes alerts on the Emory Status Page. Users should verify this resource before contacting support.

   • Kronos Workforce Central (WFC) Support (Secondary Tier)
     • Phone: +1 (866) 929-4766 (U.S./Canada) or +1 (404) 264-6700 (direct line for Emory-specific issues). Hours: 7:00 AM–7:00 PM ET, Monday–Friday.
     • Email: emory.kronos.support@ukg.com (response within 48 hours for non-urgent tickets).
     • Escalation Path: For unresolved issues after 48 hours, users must provide case numbers to Emory IT for further intervention.
   • Response Time Expectations:
     • Critical issues (e.g., locked accounts, data corruption): Resolution within 4 hours (24/7 coverage).
     • Non-critical issues (e.g., password resets, browser compatibility): Resolution within 24–48 hours during business hours.
     • Weekend/holiday support: Limited to critical outages; standard response times apply upon reopening.

   Diagnostic Decision Tree for Kronos Login Failures

   Systematic troubleshooting minimizes downtime by isolating the root cause of login failures. Below is a hierarchical decision tree to guide users through common issues, from credential verification to system-wide checks.
   

   • Step 1: Verify Credentials and Device
     • Is the Emory NetID and password correct?
       • Yes: Proceed to Step 2.
       • No: Reset the NetID or password via the Emory Password Reset Portal. Warning: Password resets may require identity verification (e.g., security questions, MFA).
     • Is the device used for login recognized by Emory’s systems?
       • Yes: Proceed to Step 2.
       • No: Register the device via Emory Duo Mobile or add it to trusted devices in the Emory MFA Portal.
     • Is the browser up-to-date and compatible with Kronos?
       • Supported Browsers: Google Chrome (latest 2 versions), Mozilla Firefox (latest 2 versions), Microsoft Edge (Chromium-based), or Safari (latest version).
       • Action: Clear cache/cookies or use an incognito window to test.
   • Step 2: Check for System-Wide Issues
     • Is Kronos experiencing a known outage?
       • Yes: Monitor the Emory Status Page for updates. Contact Emory IT if the issue persists beyond the announced duration.
       • No: Proceed to Step 3.
     • Is the VPN or network connection stable?
       • For On-Campus Users: Ensure Wi-Fi (e.g., "Emory" or "Emory-Guest") is connected.
       • For Remote Users: Verify VPN access via Emory GlobalProtect. Test connectivity with Emory’s Network Diagnostic Tool.
   • Step 3: Advanced Troubleshooting
     • Are error codes or messages displayed?
       • Common Codes:
         • 500/503: Server-side error; refresh the page or try later.
         • 403: Permission denied; verify role assignments in Kronos with a supervisor.
         • Auth-001: Authentication failure; check MFA setup or contact IT.
       • Action: Note the exact error message and timestamp for IT support.
     • Has the account been locked or disabled?
       • Check: Attempt login 3 times to trigger a lockout (Emory’s threshold: 5 failed attempts).
       • Action: If locked, wait 15 minutes or request an unlock via Emory IT Service Desk.
     • Is the issue specific to Kronos or other Emory systems?
       • Yes (Kronos-only): Clear browser data or use a different device.
       • No (University-wide): Contact Emory IT immediately, as this may indicate a broader authentication failure.
   • Step 4: Escalation to IT Support
     • If all steps fail, prepare the following details for support:
       • Timestamp and exact error message.
       • Browser/device/OS details (e.g., "Windows 11, Chrome v120").
       • Recent changes (e.g., password reset, new device added).
       • Confirmation of MFA setup (e.g., "Duo Push approved at 10:30 AM").

   Script for Describing Login Issues to IT Support

   To expedite issue resolution, users should provide structured information to IT support. Below is a template to ensure all critical details are included:
   

   • 1. User Identification
     • Full name and Emory NetID (e.g., jdoe12@emory.edu).
     • Employee ID (if applicable) or department.
   • 2. Problem Description
     • Exact error message (copy-paste if possible). Example:

       "Error: Auth-001 – Invalid credentials. Please
       

       Mobile and Remote Access Considerations for Emory Kronos

       Accessing Emory Kronos via mobile devices or remote locations requires adherence to institutional security policies while optimizing functionality for time-sensitive workflows. The Kronos mobile application (iOS/Android) and web browser access each offer distinct advantages, with compatibility constraints influenced by Emory’s VPN requirements. Proper device configuration and VPN management ensure seamless remote operations, while app notifications enhance productivity for time-tracking and approval workflows.
       

       Comparison of Kronos Mobile App and Web Browser Access

       The Kronos mobile application and web browser access serve different operational needs, with variations in security, functionality, and compatibility.

       Functionality and User Experience

       • Mobile App (iOS/Android)
         • Optimized for on-the-go time tracking, punch management, and approvals with offline capabilities in select regions.
         • Supports push notifications for timecard deadlines, approval requests, and schedule changes.
         • Geofencing options may integrate with Emory’s location-based policies for remote work verification.
         • Limited reporting and administrative features compared to the desktop version.
       • Web Browser Access
         • Full access to Kronos Workforce Central features, including advanced reporting, payroll integration, and administrative tools.
         • Compatible with Emory’s VPN for secure remote access, ensuring compliance with IT policies.
         • Requires stable internet connectivity; performance may degrade on slower networks.
         • Supports multi-monitor setups and keyboard shortcuts for efficiency in bulk operations.

       Security and Compliance

       • Mobile App
         • Encrypted data transmission and storage aligned with Emory’s IT security standards.
         • Device-level security enforced via Emory’s Mobile Device Management (MDM) policies, including mandatory encryption and passcode requirements.
         • Restricted access to certain features (e.g., PTO approvals) based on user roles.
       • Web Browser
         • Access controlled via Emory’s VPN, ensuring end-to-end encryption for data in transit.
         • Multi-Factor Authentication (MFA) mandatory for all logins, with additional IP-based restrictions for high-risk actions.
         • Browser-based security extensions (e.g., Emory’s secure token) may be required for sensitive transactions.

       Compatibility with Emory’s VPN

       • The Kronos mobile app does not require VPN for basic time-tracking but may prompt VPN redirection for administrative actions or sensitive data access.
       • Web browser access mandates VPN connectivity for all operations, with potential latency if the device lacks a stable connection to Emory’s network.
       • VPN Impact on Performance

         VPN tunnels can introduce latency, particularly on mobile networks. Emory recommends using a wired Ethernet connection for web-based Kronos access when possible.

       Configuring Kronos on Personal Devices

       Personal devices used to access Emory Kronos must comply with IT security policies to prevent data breaches. Below are the steps to configure the Kronos app or browser while adhering to Emory’s guidelines.

       Device Registration and Encryption

       • Prerequisites for Mobile Devices
         • Enrollment in Emory’s Mobile Device Management (MDM) system via the Emory Secure portal.
         • Device encryption enabled (automatic on iOS; manual setup required for Android via Settings > Security > Encryption).
         • Passcode or biometric authentication (Face ID/Fingerprint) configured with a minimum 6-digit complexity.
       • Installing the Kronos Mobile App
         • Download from the official App Store (iOS) or Google Play Store (Android) using the Emory-approved links.
         • Sign in using Emory’s single sign-on (SSO) credentials (e.g., NetID@emory.edu format).
         • Complete the initial setup, including enabling location services if geofencing is required by your department.
       • Browser Configuration for Web Access
         • Use Google Chrome or Mozilla Firefox (preferred for compatibility with Emory’s VPN).
         • Disable browser extensions that may conflict with Kronos (e.g., ad blockers, script managers).
         • Enable Enterprise Mode in Internet Explorer (if required by legacy Kronos features) via Emory’s IT support.

       Emory IT Policy Compliance Checklist

       Requirement	Action for Mobile App	Action for Web Browser
       Device Encryption	Verify via Settings > Security (Android) or About > Storage > Encryption (iOS).	N/A (applies to mobile devices only).
       VPN Enforcement	Automatically prompted for VPN when accessing restricted features.	Mandatory for all logins; configure via Emory VPN Client.
       MFA Enforcement	Enabled via Kronos app login (Duo Security or Emory Authenticator).	Required for all web logins; configure in Emory’s MFA portal.
       Data Backup	Enable iCloud (iOS) or Google Drive (Android) backups for app data.	N/A (browser data synced via Emory’s SSO).

       VPN Requirements and Troubleshooting Remote Access Issues

       Emory’s VPN ensures secure remote access to Kronos but may introduce connectivity challenges. Below are key considerations and troubleshooting steps for stable remote operations.

       VPN Impact on Login Stability

       • Common Causes of Connection Drops
         • Unstable internet connection (e.g., Wi-Fi interference, mobile data throttling).
         • VPN client conflicts with firewall or antivirus software on the device.
         • Server-side throttling due to high remote access volume during peak hours.
         • Inactive VPN sessions after prolonged periods of inactivity.
       • Recommended VPN Settings for Kronos Access
         • Use Emory’s AnyConnect VPN (preferred for reliability).
         • Enable Split Tunneling to route Kronos traffic through the VPN while allowing other apps to use local networks.
         • Avoid public Wi-Fi for VPN connections; use a dedicated Ethernet or 5G hotspot if possible.
         • Set VPN reconnection intervals to 300 seconds (5 minutes) to prevent session timeouts.

       Troubleshooting Steps for VPN-Related Issues

       • Step 1: Verify VPN Connection

         Run the command ping emory.edu in Command Prompt (Windows) or Terminal (Mac/Linux) to check connectivity. A successful ping indicates the VPN is active.

       • Step 2: Clear Browser/VPN Cache
         • Close all browser tabs and restart the VPN client.
         • For Chrome/Firefox, clear cached data via Settings > Privacy > Clear Browsing Data.
       • Step 3
         

         Integration with Emory Systems and Third-Party Tools

         Kronos Workforce Ready at Emory University serves as a centralized platform for time and attendance, scheduling, and workforce management, but its full functionality relies on seamless integration with other institutional systems. These integrations streamline workflows, reduce manual data entry, and ensure consistency across HR, payroll, and administrative processes. Below, the synchronization mechanisms, single sign-on (SSO) configurations, and third-party tool dependencies are detailed, along with a visual representation of data flow during login and authentication.
         

         Synchronization with Emory’s Core Systems

         Kronos integrates with Emory’s primary enterprise systems—Workday (HRIS), Banner (student/employee records), and Emory Email (Microsoft 365)—to maintain real-time data accuracy. The synchronization process ensures that employee records, payroll details, and access permissions are automatically updated across platforms, minimizing discrepancies and administrative overhead.

         Key Integration Points:

         • Workday (Human Resources Information System)
           Kronos pulls employee master data (e.g., job codes, compensation, department assignments) from Workday via secure API connections. Changes in Workday—such as hiring, promotions, or terminations—trigger updates in Kronos within 24–48 hours, ensuring payroll and scheduling reflect the latest organizational structure.

           Data Flow: Workday → Kronos (Employee Records, Compensation, Job Codes) → Banner (for cross-referencing student/faculty status).

         • Banner (Student and Employee Database)
           For faculty and staff with dual roles (e.g., instructors in Banner and employees in Workday), Kronos cross-references Banner data to validate appointment types (e.g., adjunct vs. full-time). This prevents scheduling conflicts and ensures compliance with university policies, such as FTE (Full-Time Equivalent) reporting.
         • Emory Email (Microsoft 365)
           Kronos does not directly sync with email accounts but relies on Emory’s SSO infrastructure (Azure AD) to authenticate users. Email notifications (e.g., timecard approvals, schedule changes) are sent via the Emory Office 365 system, using the user’s `@emory.edu` credentials for delivery.
         Impact on Login Credentials:
         • Credential Consistency: Users access Kronos using their Emory NetID and password, which must align with Workday and Banner credentials. A password reset in one system (e.g., Workday) invalidates access across all integrated platforms until updated.

           Best Practice: Use Emory’s Password Manager or Duo MFA to ensure credentials remain synchronized. Avoid setting separate passwords for Kronos unless required by a departmental exception.

         • Role-Based Access: Permissions in Kronos (e.g., manager vs. employee) are derived from Workday’s job profiles and Banner’s appointment types. Changes in these systems propagate to Kronos within 1–3 business days.

         Single Sign-On (SSO) Configuration for Kronos Access

         Emory’s SSO framework, powered by Microsoft Azure Active Directory (Azure AD), eliminates the need for separate login credentials by authenticating users once across all integrated applications. Kronos leverages SAML 2.0 for SSO, enabling seamless transitions between Workday, Kronos, and other Emory services without re-entering credentials.

         SSO Workflow:

         • Authentication Initiation:
           Users access Kronos via the Emory SSO portal (https://sso.emory.edu) or direct links in Workday/Email. The system redirects to Azure AD for multi-factor authentication (MFA) before granting access.
         • Token-Based Authorization:
           Upon successful MFA, Azure AD issues a SAML assertion containing user attributes (e.g., NetID, role). Kronos validates this token to determine access levels (e.g., timekeeper, supervisor, admin).
         • Session Management:
           SSO sessions persist for 8 hours or until the user closes the browser. Subsequent logins to other Emory systems (e.g., Workday) reuse the same session if within the same device/browser.
         Configuring SSO for Third-Party Tools:
         To enable SSO for tools integrated with Kronos (e.g., calendar apps, payroll systems), follow these steps:
         1. Verify Azure AD App Registration:
            Ensure the third-party tool is registered in Azure AD with the correct SAML metadata. For Kronos, the metadata URL is:

            https://[your-company].kronos.com/saml2/metadata

            (Replace `[your-company]` with Emory’s Kronos subdomain, e.g., `emory.kronos.com`.)
         2. Map User Attributes:
            Configure Azure AD to send Kronos-specific attributes (e.g., `employeeID`, `department`) via the SAML response. Example attribute mapping:

            Azure AD Attribute	Kronos Attribute	Purpose
            userPrincipalName	NetID	Primary login identifier
            extensionAttribute1	Employee Number	Workday sync identifier
            department	Department Code	Scheduling/payroll categorization

         3. Test SSO Integration:
            Use Azure AD’s SSO Test Tool to simulate login flows and validate token exchange. For Kronos, test the following endpoints:

            https://[emory].kronos.com/sso/saml2/login

         4. Enable Just-In-Time (JIT) Provisioning (Optional):
            For tools requiring Kronos data (e.g., payroll systems), configure JIT provisioning in Azure AD to auto-create accounts based on Kronos attributes.

         Third-Party Tools Requiring Kronos Login

         Several external and internal tools at Emory rely on Kronos for data input or authentication. These include:
         • Payroll Systems (e.g., ADP, Workday Payroll):
           Kronos timecards and schedule data feed into Workday Payroll via HL7 or CSV exports. Employees must log into Kronos to submit timecards, which are then processed in Workday for payroll calculations.

           Setup Steps:

           1. Ensure the Kronos Payroll Interface is enabled in Workday under Payroll Setup.
           2. Configure automated exports in Kronos to push time data to Workday’s Payroll Integration Center nightly.
           3. Validate mappings between Kronos job codes and Workday compensation elements.

         • Calendar and Scheduling Tools (e.g., Google Calendar, Outlook):
           Kronos schedules can be synced to Microsoft Outlook or Google Calendar via iCal/ICS feeds or Kronos API. Managers use these integrations to auto-populate meetings based on employee schedules.

           Example: Outlook Integration

           1. Generate an iCal feed in Kronos (Admin → Integrations → Calendar Sync).
           2. Add the feed URL to Outlook under File → Open & Export → Import/Export.
           3. Set synchronization frequency (e.g., daily) to reflect Kronos updates.

         • Biometric and Badge Systems (e.g., Kiosk Time Clocks):
           Physical time clocks (e.g., in labs or retail operations) sync with Kronos via USB, Wi-Fi, or API. Employees log in using Emory NetID + MFA before clocking in/out.

           Configuration Requirements:

           • Ensure the device is IP-whitelisted

             Mastering the Kronos login process at Emory transcends mere technical proficiency; it embodies a strategic alignment between institutional workflows and individual responsibilities. By adhering to the structured steps outlined—from credential verification to MFA configuration and remote access optimization—users can minimize downtime and enhance operational efficiency. Proactive troubleshooting, adherence to security best practices, and leveraging Emory’s support systems ensure that Kronos remains a reliable tool for time management, payroll, and HR coordination. As digital integration deepens across university systems, this guide serves as a foundational resource to navigate Kronos with confidence and precision.