An enterprise customer support organization recently transferred a Senior Support Manager to an unassociated international subsidiary. The Salesforce Administrator needs to immediately restrict this user's ability to log in to the org during an offboarding security evaluation. However, during an administrative check, the administrator discovers that the manager is currently designated as the Default Case Owner in Support Settings and is referenced as the target user in several active Case Escalation Rule actions. Which action should the administrator take to prevent log-in access immediately without disrupting existing automated case management processes?
- Freeze the user account immediately, reassign the Default Case Owner setting and Escalation Rule actions to another active user, and then deactivate the user account.Cevap
- BDeactivate the user account immediately, which automatically transfers the Default Case Owner setting to the System Administrator profile.
- CDeactivate the user account immediately, as Salesforce allows deactivating users assigned as Default Case Owners while retaining historical routing rules.
- DDelete the user record from Setup, which automatically strips all administrative references from Support Settings and active Case Escalation Rules.
Cevap
Freeze the user account immediately, reassign the Default Case Owner setting and Escalation Rule actions to another active user, and then deactivate the user account.
Freezing a user account immediately blocks login access while leaving license allocation and system references unchanged. This allows the administrator to address system dependencies—such as the Default Case Owner setting in Support Settings and active Case Escalation Rules—without leaving an active security vulnerability. Once dependencies are reassigned to another active user, the account can be safely deactivated.
Adım Adım Çözüm
Anahtar Kavram
Freezing vs. Deactivating Users with System Dependencies
Tahmini Süre:2m 0s