Peakline's customer data is valuable, so Jay wants to make sure only the right people get in, at the right times, from the right places. That's login security, and the biggest lock of all is MFA.
Password policies
In Setup, Password Policies let Jay make passwords strong:
- how long they must be, and how complex
- how often they expire
- how many wrong tries lock someone out
A profile can have its own password policy, and that one wins for its users.
Multi-factor authentication
Multi-factor authentication (MFA) means two proofs instead of one:
- something you know, like your password
- something you have, like an app on your phone or a security key
Salesforce requires MFA for internal users who log in to its user interface. So when Jason logs in, he types his password, then approves the login on his phone.
Login hours and IP ranges
| Setting | Where | What it does |
|---|---|---|
| Login hours | On the profile | The times its users can log in |
| Login IP ranges | On the profile | The network addresses they can log in from. Outside them, they're blocked |
| Trusted IP ranges | Network Access | Softer: from outside them, users can still log in after verifying who they are |
Recap
- Password policies make passwords strong.
- MFA adds a second proof, and Salesforce requires it for internal users.
- On each profile, login hours and IP ranges control when and where people get in.
Now you try
In your org, open Setup, find Password Policies, and check how many wrong tries lock a user out. Share the number in the video's comments, or reply STUCK.