User Management Settings is a Setup page of independent toggles. You do not create a record here. You enable the org-wide user features your policies call for. Open the page, switch on what you need, and pair risky options with a documented plan.
- Open the page
From Setup, in the Quick Find box, search for User Management Settings and select it. It sits in the Manage Users and Data Access section. You need an admin profile or the equivalent setup permissions to see it.
- Turn on the convenience features first
Enable the enhanced list views you want, such as Enhanced User List Views and Enhanced Profile List Views, plus the Enhanced Profile User Interface if your team prefers it. These carry no privacy risk and speed up daily admin work.
- Enable governed features with a policy behind them
For options like Enable User Self-Deactivation, the Email Domain Allowlist, User Access Policies, or Let Users Scramble Their User Data, confirm the matching policy exists first. Save the page, then build any supporting flow or component the feature needs.
- Document and test
Record why each toggle is on and who approved it. Test self-deactivation and any obfuscateUser call in a sandbox before production, since scrambling user data cannot be undone.
Upgrade Setup lists into interactive grids that support inline editing, filtering, and column customization for faster bulk admin.
Enables the System.UserManagement.obfuscateUser Apex method to permanently anonymize a user's personal data. The action is irreversible.
Lets external Experience Cloud and Chatter users deactivate their own accounts, with the same effect as admin deactivation.
Restricts which email domains are allowed in user records so accounts cannot be provisioned on unapproved domains.
Automates assigning users to permission sets, permission set groups, and licenses based on criteria you define.
- Scrambling with obfuscateUser is permanent. Once invoked, the user's data is anonymous and can never be recovered, so test in a sandbox and require sign-off.
- Self-deactivation only covers external Experience Cloud and Chatter users, not internal employees, and it leaves the user record (and its owned records) in place.
- Enabling self-deactivation is not enough on its own. You still have to expose it through the Customizable User Settings component or a custom flow for users to actually trigger it.
- Most toggles are org-wide and quiet, so an undocumented change is hard to spot later. Note why each enabled option is on.