Zum Inhalt springen

What Stays on the Profile, Health Check and Security Center

Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.

Module 5 of 5 in the shared chapter The Front Door: Logging In to Salesforce, chapter 2 of Securing Salesforce: Sharing and Visibility and part of the Identity and Access course. Each module stands on its own.

The question this module answers: Where do the front door’s settings live, how do you check that the door is set well, and what changed at the door in 2025 and 2026?

The last four modules set up the front door: who you are, from where, when, for how long, and for which kind of user. Two questions are left. Where do all those settings live? And once they’re set, how do you know the door is still set well next month?

The profile keeps the door; permission sets carry the keys

Section titled “The profile keeps the door; permission sets carry the keys”

When you open a profile and a permission set side by side, a lot of it looks the same. But not everything. The session settings, the password policies, the login hours and the login IP ranges are kept exclusive to the profile. You won’t find them on a permission set.

Here’s the rule of thumb I use to remember which goes where. Something you can have many of will probably end up on a permission set. Something you can only have one of will probably be on the profile. You can have many permission sets, so they carry the keys: access to objects, fields, apps and tabs, and permissions like the one that requires MFA for screen logins. You have only one profile, so it holds the things that can only have one answer for a user: one password policy, one session timeout, one set of login hours, one set of login IP ranges, one default app.

Salesforce’s guidance draws the same line. After cancelling its plan to retire permissions on profiles, it recommends “a least-privilege model using profiles for baseline settings and permission sets for access control.” On the profile: default apps, default record types and page layouts, login hours, login IP ranges, password policies and session settings. In permission sets and permission set groups: object permissions, field-level security, user permissions and the rest of the access (Permissions in Profiles Retirement Cancelled (opens in a new tab), Salesforce Help, published 2026-06-06, checked 2026-11-01).

The profile keeps the door; permission sets carry the keys Two columns. The profile, one per user, the door: login hours, login IP ranges, password policies, session settings, the default app, default record types and page layouts. Permission sets, many per user, the keys: object permissions, field-level security, user permissions such as MFA for screen logins, apps and tabs. Footnote: many of something goes on a permission set; only one of something stays on the profile. {"author": "Steve Simpson", "blueprint": "1.0.0", "builder": "standard 1.52.0", "built": "2026-10-28", "id": "DGM-SHR-FD-15", "rights": "\u00a9 2026 Twinshark LLC. All rights reserved.", "template": "comparison 0.5.0", "theme": "stevetecharc 1.4.0"} The profile: one per user the door Login hours Login IP ranges Password policies Session settings The default app Default record types and page layouts Permission sets: many per user the keys Object permissions Field-level security User permissions, such as MFA for screen logins Apps and tabs Many of something: a permission set. Only one of something: the profile. © 2026 Twinshark LLC · stevetecharc.com
Click to enlarge

That’s why every module in this chapter kept saying “on the profile.” The door is set per profile, and chapter 3 of this course goes deep on profiles, permission sets and permission set groups.

Settings drift. Someone loosens a password rule to fix a complaint, someone lengthens a session timeout for a demo, and nobody changes it back. So you need a way to check the door, not just set it.

That’s Health Check, in Setup. In Salesforce’s words, “you can use Health Check to identify and fix potential vulnerabilities in your security settings, all from a single page.” It compares your settings with a baseline, either the Salesforce Baseline Standard or one of up to five custom baselines you upload, and gives you a score and a grade. Its settings are sorted into high-risk, medium-risk, low-risk and informational ones, and Fix Risks can change settings to the baseline’s values without leaving the page. Salesforce also adds new checks from time to time, so the score can change even when you haven’t (Security Health Check (opens in a new tab), Salesforce Help, checked 2026-11-01).

It also watches for you now. Since 15 April 2026, Health Check notifications are on by default for System Administrators in production orgs: a weekly alert if your score goes down (Stay Secure with Proactive Health Check Notifications (opens in a new tab), Salesforce Spring ‘26 release notes, checked 2026-11-01). Don’t turn them off. A score that drops on a Tuesday is a door someone opened on a Monday.

A word of judgment, though: a high score isn’t the goal. The baseline is Salesforce’s general recommendation. A custom baseline that matches your company’s own policy, and a score you understand, are worth more than a perfect number.

Health Check: is the door still set well? Top to bottom: your org's security settings, such as passwords, sessions, login hours and IP ranges, are compared with a baseline, the Salesforce Baseline Standard or your own. Health Check gives a score and a grade, with settings sorted from high risk to informational. Then two paths: fix risks now, changing settings to the baseline from the same page; and a weekly notification to admins when the score drops; both lead to a door that stays set well, checked, fixed and watched. Footnote: a score that drops on a Tuesday is a door someone opened on a Monday. {"author": "Steve Simpson", "blueprint": "1.0.0", "builder": "standard 1.52.0", "built": "2026-10-28", "id": "DGM-SHR-FD-16", "rights": "\u00a9 2026 Twinshark LLC. All rights reserved.", "template": "flow/sequence 0.1.0", "theme": "stevetecharc 1.4.0"} Your org's security settings passwords, sessions, login hours, IP ranges, and more Compared with a baseline the Salesforce Baseline Standard, or your own A score and a grade settings sorted from high risk to informational Act on it Fix Risks change settings to the baseline, from the same page A weekly notification to admins, when the score drops A door that stays set well checked, fixed and watched now every week A score that drops on a Tuesday is a door someone opened on a Monday. HOW TO READ IT a step the step that matters most a choice a path what comes next © 2026 Twinshark LLC · stevetecharc.com
Click to enlarge

Health Check tells you how the door is set. Login History, in Setup, tells you who actually came through it, when, from where and how. Since the MFA rollout, you can add columns for the strength signals an identity provider sends, the same ones module 2 described, so you can see whether single sign-on logins are arriving as strong as you think. The same values are in Event Monitoring’s login events (Prepare for MFA Enforcement for All Employee Users (opens in a new tab), Salesforce Help, checked 2026-11-01). Chapter 19 of this course covers monitoring in depth.

If a company has many orgs, checking each door one by one doesn’t scale. Security Center “offers a single view of your security, privacy, and governance posture across all of your Salesforce orgs and tenants”: Health Check scores, access settings, and user and login metrics in one place. It’s an add-on, available in Enterprise and Unlimited Editions with the Security Center license, and free in Developer Edition (Take Charge of Your Security Goals with Security Center (opens in a new tab), Salesforce Help, checked 2026-11-01). If you’re the architect for a company with ten orgs, it’s worth the conversation.

The door has changed more in the last year than in the five before it. Here’s the summary, each change dated and covered in this chapter. Dates are Salesforce’s, and some rolled out by release group over several weeks, so check what applies to your org.

What changed at the front door, 2025–2026 A timeline, top to bottom, with what each change means beside it. From 20 November 2025, anonymizing VPNs and high-risk IP addresses are blocked, and API traffic from them too from 24 April 2026: an integration behind an anonymizing VPN freezes its own user. Spring '26: new connected apps need a request to Support: register new integrations as External Client Apps. 15 April 2026: Health Check notifications on by default: admins hear when the score drops. From 1 July 2026: step-up to view and export reports: prove it again before data leaves. From 20 July 2026, highlighted: MFA for every employee login, passkeys for privileged users and a username-first login page: a password alone no longer opens the door. Winter '27: profile filtering enforced: give View All Profiles on purpose. From 4 November 2026: idle refresh tokens expire after 30 days: a stolen token has a shorter life. Footnote: production dates; many rolled out by release group over weeks; check what applies to your org. {"author": "Steve Simpson", "blueprint": "1.0.0", "builder": "standard 1.52.0", "built": "2026-10-28", "id": "DGM-SHR-FD-17", "rights": "\u00a9 2026 Twinshark LLC. All rights reserved.", "template": "flow/sequence 0.1.0", "theme": "stevetecharc 1.4.0"} From 20 November 2025 anonymizing VPNs and high-risk IPs blocked; API traffic too from 24 April 2026 An integration behind an anonymizing VPN freezes its own user. Spring '26 new connected apps need a request to Support Register new integrations as External Client Apps. 15 April 2026 Health Check notifications on by default Admins hear when the score drops. From 1 July 2026 step-up to view and export reports Prove it again before data leaves. From 20 July 2026 MFA for every employee login; passkeys for privileged users; username first A password alone no longer opens the door. Winter '27 profile filtering enforced Give View All Profiles on purpose. From 4 November 2026 idle refresh tokens expire after 30 days A stolen token has a shorter life. WHAT IT MEANS Production dates; many rolled out by release group over weeks. Check what applies to your org. HOW TO READ IT a step the step that matters most what comes next © 2026 Twinshark LLC · stevetecharc.com
Click to enlarge
WhenWhat changed at the doorWhere
From 20 November 2025; API from 24 April 2026Connections from anonymizing VPNs, proxies and high-risk IP addresses blocked; API and connected app traffic from them freezes the user and revokes refresh tokensModule 3
Spring ‘26New connected apps can’t be created without a request to Salesforce Support; External Client Apps replace themModule 1
15 April 2026Health Check notifications on by default for System Administrators in production orgsThis module
From 1 July 2026 (production, staggered)Step-up authentication to view and export reportsModule 2
From 20 July 2026 (production, by release group; some orgs extended)MFA for every employee login, including single sign-on; phishing-resistant MFA (passkeys) for privileged users; the username-first login pageModule 2
Summer ‘26 release update, enforced in Winter ‘27Profile filtering on by default; View All Profiles needed to see other profiles and to build login flowsChapter 1, module 4; module 4
From 4 November 2026 (production, rolling)Idle OAuth refresh tokens expire after 30 daysModule 1

The pattern is the same one chapter 1 described for the whole platform: the defaults are moving toward closed. Salesforce now publishes its roadmap of these controls in one place, with a change log, so that’s the page to watch (Security-Related Product Updates to the Salesforce Platform (opens in a new tab), Salesforce Help, published 2026-09-08, checked 2026-11-01).

  • Which door settings each profile carries, and that access lives in permission sets, not on the profile.
  • Which baseline Health Check measures against, the Salesforce Baseline Standard or the company’s own, and who reads the weekly notifications.
  • Who reviews Login History, and how often, especially for privileged users and single sign-on.
  • Whether a company with many orgs needs Security Center to see all its doors at once.
  • How the team hears about the next change at the door before it’s enforced.

Beyond the exam: what AI changes. Setup with Agentforce can now help an admin review the Health Check score, Salesforce notes. That’s useful, and it’s also a reminder of this course’s first lesson: a tool can tell you what a setting is, but an architect still decides what it should be, and why.