An administrator at a financial institution must immediately prevent a regional director from logging into Salesforce due to an unannounced compliance audit. However, the director is currently set as the Default Lead Owner for Web-to-Lead, the running user for critical nightly scheduled Apex jobs, and a specified user in custom hierarchy fields used by active approval processes. Deactivating the user immediately causes validation errors and breaks automated background processes. What action should the administrator take to instantly block access without disrupting ongoing system operations?
- Freeze the user account to temporarily prevent login access while leaving system background tasks, approval rules, and default ownership references unaffected.Cevap
- BDeactivate the user account, as Salesforce automatically reassigns all running background Apex jobs and default lead ownership settings to the System Administrator.
- CChange the user's Profile to a read-only profile with zero active permissions so that scheduled Apex jobs and lead routing continue without allowing logins.
- DDelete the user record from Setup to instantly revoke login rights, release the license, and purge all automated workflow references.
Cevap
Freeze the user account to temporarily prevent login access while leaving system background tasks, approval rules, and default ownership references unaffected.
Freezing a user account prevents the user from logging in immediately while preserving their license and allowing all existing background automated processes, scheduled jobs, default ownerships, and custom hierarchy references to run without error.
Adım Adım Çözüm
Anahtar Kavram
User Freezing vs. User Deactivation