If a user's assignment to an app integration changes from individual to group, what will happen to their downstream application account?

When a user's assignment to an app integration switches from individual to group, the user account within the downstream application will remain active. This is because changing the assignment type does not inherently trigger a deactivation of the user’s account; rather, it shifts the access management to be governed by the group's settings and permissions.

As a result, any entitlements, applications, or access privileges linked to the user are not automatically revoked when this change occurs. The user retains their access to the application they were originally assigned to as their individual status was merely replaced with group membership. This ensures continuity in access and preserves the user's ability to utilize the application without interruption. Any configurations tied to the individual user should still apply as long as the group’s permissions align appropriately.

It's important to understand that while an individual user can gain or lose access based on group membership updates, the account itself will generally remain active and will not be deactivated unless there are additional policies or triggers defined in the application settings that specifically instruct otherwise.