Why structured user management matters
"I just hired three new reps and promoted one to team lead. I need their access sorted before their first call this afternoon โ not after a week of back-and-forth IT tickets."
Getting access wrong in either direction is costly: too little access and new hires are blocked from doing their job; too much and sensitive data is exposed to people who shouldn't see it.
Anatomy of a user account
Every user is built from three ingredients that work together โ not one all-or-nothing setting:
| Ingredient | Controls |
|---|---|
Role โ ADMIN / MANAGER / SALES_USER | ADMIN bypasses all profile-based checks entirely; the other roles are governed by their Profile |
| Manager (for Sales Users) | Builds the reporting chain used by role-hierarchy sharing โ a manager automatically sees their reports' records |
| Profile | Governs exactly which objects, fields, apps, and tabs the user can see or edit (covered in depth in the Profiles & Permissions trail) |
Deleting a user does not delete the records they created โ that history remains intact, with the original username preserved as the "created by" value even after the account is gone.