BambooHR Users Deactivated in Okta When the Deactivation Option Is Set to Do Nothing or Suspend
Last Updated:
Overview
Okta deactivates BambooHR users even when the When a user is deactivated in the app option is set to Do nothing or Suspend because the user has a Staged status and falls outside the configured Pre-Start Interval. Prevent this deactivation by ensuring the user status is Active or Pending user action, or by adjusting the Pre-Start Interval to include the hire date.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- BambooHR
- Lifecycle Management
- Import
Cause
BambooHR acts as a profile source and performs Okta user offboarding actions, such as suspending or deactivating Okta users, when the Profile & Lifecycle Sourcing option is enabled and the BambooHR application assignment is removed in Okta. This removal occurs due to a BambooHR user termination status found during a subsequent import, a future hire date that does not meet the configured Pre-Start Interval, or a manual removal of the application assignment.
The Hire Date is managed in the Okta integration using the Pre-Start Interval option. Users with a Hire Date within this interval are considered active and imported to Okta. For example, if the interval is set to 7, users with a Hire Date later than one week ahead of the current date are not imported. Any Okta user assigned to the BambooHR integration that is not part of the BambooHR import is deactivated in Okta.
Solution
How is the BambooHR user deactivation resolved?
The deactivation occurs because the Okta user status is set to Staged. Users with the Active or Pending user action status are not affected by this behavior. Ensure the user status is Active or Pending user action to prevent deactivation when the When a user is deactivated in the app option is set to Suspend or Do nothing.
