When an SSO configuration is disabled or replaced with a new one, users who are enrolled in the old configuration silently lose access to their projects. There is no in-product warning at the point of making the change, and no notification reaches the affected users. The admin who makes the SSO change may not realise that existing enrolled users need to be manually re-enrolled in the new configuration.
When an admin disables or deletes an SSO configuration that has users enrolled in it, Document360 should display a warning listing the users who will lose access to their projects as a result. The admin should be required to acknowledge this list before the change takes effect. Optionally, Document360 could surface a prompt offering to send a notification to the affected users, or display the list of affected users in a downloadable format for follow-up.
Benefit: Admins can anticipate and act on access disruption before it affects users, rather than discovering it after users have already lost access and require manual remediation.