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 is costly either way. Give someone too little access, and they're blocked from doing their job. Give them too much, and sensitive data ends up in front of people who shouldn't see it.
Anatomy of a user account
Every user's access comes from three things working together โ not one single all-or-nothing setting:
| Ingredient | Controls |
|---|---|
Role โ ADMIN, MANAGER, or SALES_USER | ADMIN skips all profile checks completely and can do anything. The other two roles follow whatever their Profile allows |
| Manager (only set for Sales Users) | Sets up the reporting chain used for "sharing-by-role" โ a manager automatically sees the records that belong to the people who report to them |
| Profile | Controls 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 stays intact โ the original username is kept as the "created by" value, even after the account itself is gone.