An administrator at a logistics enterprise needs to temporarily block login access for an operations manager who is taking a three-month sabbatical. The user account is currently designated as the Default Web-to-Case Owner and is referenced in active lead assignment rules. Attempting to deactivate the user immediately triggers administrative errors due to these system dependencies. Which course of action should the administrator take to resolve this issue while maintaining system automation?
- Freeze the user account from the User detail page to prevent login access without affecting automated processes or record assignments.Answer
- BDeactivate the user account after removing the user's assigned role and license to bypass system dependency validations.
- CAssign a restricted custom profile to the user that revokes the API Enabled and System Administrator administrative permissions.
- DRestrict the Login IP Ranges on the user's profile to prevent login attempts outside the corporate network.
Answer
Freeze the user account from the User detail page to prevent login access without affecting automated processes or record assignments.
Freezing a user account prevents login access instantly while retaining the user ID in active automated workflows, default case ownership configurations, and assignment rules. This provides an immediate solution when deactivation is blocked by system dependencies.
Step-by-Step Solution
Key Concept
User Account Freezing vs. Deactivation