ADM-201 · Question #260
An administrator at Cloud Kicks wants to deactivate a user who has left the company. What are two reasons that would prevent a user from being deactivated? Choose 2 answers
The correct answer is C. The user is assigned in a workflow email alert. D. The user is in a custom hierarchy field. A user cannot be deactivated if they are referenced in active system configurations such as workflow email alerts or custom hierarchy fields.
Question
An administrator at Cloud Kicks wants to deactivate a user who has left the company. What are two reasons that would prevent a user from being deactivated? Choose 2 answers
Options
- AThe user is the highest role in the role hierarchy.
- BThe user is part of a territory hierarchy.
- CThe user is assigned in a workflow email alert.
- DThe user is in a custom hierarchy field
How the community answered
(26 responses)- A4% (1)
- B4% (1)
- C92% (24)
Why each option
A user cannot be deactivated if they are referenced in active system configurations such as workflow email alerts or custom hierarchy fields.
Being the highest role in the role hierarchy does not prevent deactivation; the role can be reassigned or left vacant.
Membership in a territory hierarchy does not block user deactivation; their territory assignments can be updated or removed.
If a user is designated as a recipient in a workflow email alert, they cannot be deactivated because the system requires an active user for the alert to function correctly.
When a user is selected in a custom hierarchy field (e.g., a custom 'Manager' field), deactivating them would break the defined hierarchical relationship, preventing deactivation.
Concept tested: User Deactivation Restrictions
Source: https://help.salesforce.com/s/articleView?id=sf.users_deactivate.htm&type=5
Topics
Community Discussion
No community discussion yet for this question.