BambooHR can be used as a Profile Source in Okta when the "Profile & Lifecycle Sourcing" option is enabled. This allows BambooHR to perform Okta user off-boarding actions such as suspend or deactivate Okta users when the Okta end user's BambooHR app assignment is removed in Okta due to one of the following: 

• BambooHR user termination status found during subsequent BambooHR import job execution.
• Having a new/updated BambooHR user with a future hire date that does not meet the currently configured BambooHR Pre-Start Interval.
• Okta Admin manually overrides and removes BambooHR app assignments (individual/group) as necessary.

When the "When a user is deactivated in the app" option is set to "Suspend User" or "Do nothing", the Okta users are still deactivated. This article explains why.

      OR  

• BambooHR
• Lifecycle Management
• Import

The "Hire Date" is managed in the Okta integration using the "Pre-Start Interval" option. Users with a "Hire Date" within this interval will be considered active and imported to Okta.

• For example, if entered 7, the users with a "Hire Date" later than one week ahead of the current date will not be imported. Any Okta user assigned to the BambooHR integration that is not part of the BambooHR import will be deactivated in Okta. 

• The deactivation is caused by the Okta user status being set to "Staged".
• Users with the "Active" or "Pending user action" status will not be affected.

Related References

• New BambooHR users are not imported into Okta