The To Okta application lifecycle setting allows administrators to define the action Okta takes when a source application deactivates a user. The When a user is deactivated in the app setting provides the options Deactivate, Suspend, or Do Nothing. Understanding the differences between the deactivated and suspended states is critical for managing downstream application access and user profiles.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Lifecycle Management
• Provisioning

How do the deactivated and suspended states affect downstream applications?

When configuring the To Okta application lifecycle setting, administrators must choose the action Okta performs when a source application deactivates a user. The selected state impacts downstream application access and user profile management.

• Deactivated: When Okta deactivates a user, Okta removes all application assignments and permanently deletes the user's password. The user loses all access to Okta and any downstream applications managed by Okta.
• Suspended: When Okta suspends a user, the user cannot access applications through Okta, the Okta Admin Console, or the Okta End-User Dashboard. However, Okta retains all application assignments, and administrators can still update the user profile. Because Okta leaves application assignments unchanged, the end user retains access to downstream applications outside Okta and can log in directly if the application supports direct authentication.