
JoshH.04413 (Customer) asked a question.
How can we keep a user from being suspended automatically in Okta if they are going to continue on in contract work but their profile will be deactivated in BambooHR, from where we are sourcing profiles and users? They will still need access to their apps afterwards.
Normally, they would be suspended automatically in Okta once they're deactivated in BambooHR, but how can we prevent that from happening?

Hi @JoshH.04413 (Customer) , Thank you for reaching out to the Okta Community!
You could look into the option of disconnecting the account from the Profile Source.
In the Okta Admin dashboard, when you go to the user's profile page, you should see something that says "Profile Sourced by BambooHR". Example (using AD user as example):
Under "More Actions", you should see "Disconnect from BambooHR" - this would sever the connection and the user remains active and maintains the Okta User Profile attributes, but a password reset might be required if credential syncing is in place.
That being said, you would have to be aware of any downstream implication if the additional BambooHR app user profile information is used in any automations like group rules, app assignments etc.
Disconnecting the user will also mean that no updates coming from BambooHR, so you will have to manually update the user profile when needed or connect it to a different source.
If you have a paid account with us, I recommend opening a case before disconnecting the user, to go over your implementation with someone from the Support team.
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--
Help others in the community by liking or hitting Select as Best if this response helped you.