Category: Release notes

  • Manual shares can now survive an owner change, if you turn it on

    Manual shares can now survive an owner change, if you turn it on

    The short answer: Winter ’27 adds an org-wide Sharing Settings option, Keep Manual Shares When Transferring Records. It’s off by default, so nothing changes until you enable it. When it’s on, a record keeps its manual shares after the owner changes, for every record in the org. There’s no per-record control, so test before you switch it on.

    Say a rep leaves on Friday and you reassign her accounts on Monday. (It’s the same scene as who owns the records of people who left, seen from the sharing side.) Over the years she’d shared a handful of opportunities with a solutions engineer, a couple of cases with the support lead, one account with a partner manager. Monday afternoon the engineer says he can’t see the deal he’s been working all quarter. Nothing is broken. That’s how manual sharing has always behaved on an owner change, and Winter ’27 finally lets you decide otherwise.

    Features vary by edition and license. Check the release notes for your org before you rely on any of this. It’s one of the items in our Winter ’27 round-up for admins.

    What is a manual share in Salesforce?

    A manual share is access someone grants to one record, for one person, group or role, outside your sharing rules. Salesforce Help describes manual sharing as the way users share individual records when other features can’t provide the access. The owner, someone above the owner in the role hierarchy, a user with Modify All Records on the object, or an admin can grant it.

    In Lightning Experience it’s the Sharing button on the record. Underneath, it’s a row in the object’s share table with a row cause of Manual. That row cause matters later, because it’s what gets deleted.

    What used to happen to manual shares when the owner changed?

    They were deleted. Salesforce Help says that transferring a record’s ownership deletes the manual shares the original owner created, which can remove access for the people they were shared with. Transfer an account and the manual shares the old owner created on its child opportunities and cases go too.

    It applies to assignment rules as well as hand transfers. A Salesforce Help article describes a case where an Apex trigger added share rows on insert, and the case assignment rule then changed the owner and removed them. The suggested workaround was to add the rows asynchronously, after the assignment had finished. Plenty of orgs carry some version of that code.

    How do you keep manual shares in Salesforce when the owner changes?

    Go to Setup > Sharing Settings, click Edit, select Keep Manual Shares When Transferring Records, and save. Salesforce Ben reports the option is off by default and applies to all records when it’s on. Salesforce Break lists it for Lightning Experience and Classic in Professional, Enterprise, Performance, Unlimited and Developer editions.

    That’s the whole feature. No object list, no per-record flag, no expiry date. You can’t say “keep these on opportunities but not on cases”. Salesforce Ben notes the idea came from IdeaExchange and that the author wishes it went further.

    Who should turn it on, and who should leave it off?

    Our opinion: turn it on if lost access is your recurring complaint, and leave it off if disappearing access is doing a quiet job for you. Both situations are common.

    Turn it on ifLeave it off if
    Reassignments regularly break access for colleagues who work the same dealsYou rely on owner changes to clean up access, for example when a record moves teams
    You’ve written triggers or Flows only to re-create shares after a transferYour org holds records where a lingering share would be a confidentiality problem
    Territory or account reshuffles generate “I can’t see it any more” ticketsYou can’t yet say who holds manual shares today

    The second column is the one to take seriously. Salesforce’s architect post advises identifying which business processes depend on ownership changes to remove access, documenting exceptions, and confirming retained shares fit a least-privilege model. A share nobody remembers granting is easier to forget when it survives.

    How does it interact with lead and case reassignment?

    Reassignment is exactly where the old behavior bit, so test it there first. Salesforce Break’s advice is to try the setting against your territory reassignment and account transfer processes in a sandbox before production. We’d add assignment rules and any Flow that changes an owner.

    Two things we could not confirm from the sources we could open. First, whether every owner-change path, assignment-rule changes and Mass Transfer Records included, behaves the same with the setting on. Second, whether leads, which only have manual sharing when their sharing model is private, are affected differently. Check both in a sandbox. If it turns up a pile of ownership clean-up, our managed admin service covers that kind of job.

    If you’ve built custom code to re-create shares after transfers, Salesforce suggests reviewing it, since the native behavior may make it unnecessary. Don’t delete it on the first day. Run both for a release and compare.

    What can go wrong?

    Access that used to expire now stays. That’s the point, and also the risk. Someone shared a record with a contractor, the owner changed, and the contractor still has it a year later. Parent-account rules still apply too: Salesforce Help says recipients need at least Read access to the parent account to receive a share on a child record.

    Moving an opportunity or case to a different parent account can still delete its manual shares, per Salesforce Help, if the person making the change can’t share the new parent account. The setting is about owner changes, not every way a record can move.

    What to do Monday:

    1. Find out which objects have manual shares today. A SOQL query on the object’s Share table where RowCause is Manual will tell you.

    2. List every trigger and Flow that re-creates shares after a transfer.

    3. In a sandbox, enable the setting, reassign a few records through each of your owner-change routes, and check who can still see them.

    4. Decide per team, then write down why you did or didn’t switch it on.

    Where we come in

    Bosun, by GTM Cloud, assigns record owners by rules and pools, and can reassign a leaver’s records in one run and put them back. It’s in pilot and isn’t publicly listed yet. In version 1 it sets the owner only, so whether manual shares survive is the Sharing Settings option’s job, not Bosun’s. Join the Bosun pilot if reassignment is where you lose time.

    Questions people ask

    Does Keep Manual Shares apply to all records?

    Yes, according to Salesforce Ben. It’s an org-wide setting with no way to choose objects or records. When it’s off, which is the default, Salesforce keeps deleting manual shares on an owner change as before. Enable it in a sandbox first and compare.

    Does it restore manual shares that were already deleted?

    Nothing we’ve read says so. The release note describes keeping shares when ownership changes from now on. Shares already deleted would need to be granted again. If you need to know what access existed, you’d have to reconstruct it from your own records or backups.

    Is the setting generally available?

    The sources we read describe it as a Winter ’27 Sharing Settings option, off by default, with no beta label. Salesforce Ben doesn’t state a status either way. Read the release note for your org and confirm what you see in Setup before planning around it.

    Sources

  • Profile filtering is enforced in Winter ’27: what changes and how to check

    Profile filtering is enforced in Winter ’27: what changes and how to check

    The short answer: The Enable Profile Filtering release update, available since Summer ’26, is enforced in Winter ’27. Once it applies, users see only their own profile name unless they hold the View All Profiles permission. Anything that reads another user’s profile name, such as a Flow, validation rule or Apex class, can then get a blank value instead of an error.

    Say a sales manager complains that opportunities from the partner team aren’t routing to the right queue. Nothing was deployed. The Flow hasn’t changed in a year. It checks whether the record owner’s profile is “Partner Sales”, and since the update the profile name comes back empty for the person who triggered it, so the condition is never true. Nobody sees an error, which is why this one is worth testing on purpose.

    Features vary by edition and license. Check the release notes for your org before you rely on any of this. This is one item from our Winter ’27 round-up for admins.

    What does the Enable Profile Filtering release update do?

    It restricts users to seeing their own profile name. According to Salesforce Ben, they see other profiles only if they have the View All Profiles permission. Salesforce Break says the setting is enabled by default from Summer ’26, and Salesforce Ben says it was added in Summer ’26 and is enforced in Winter ’27. Setup > Release Updates > Enable Profile Filtering has the testing and activation steps.

    Salesforce Ben lists it with a note that you need to act only if users must see other profiles. That undersells the risk a little. The users don’t need to look at profiles. The code running as them does.

    Is it enforced yet, and who is affected?

    Probably, for your org. Salesforce Dictionary reports Winter ’27 production waves on September 4, October 2 and October 9, 2026. Salesforce Break’s screenshot of the Release Updates screen showed a completion deadline of September 1, 2026. Dates move, so open the Release Updates screen and read the status rather than trusting any post, this one included.

    You’re affected if something running as a user without the permission reads another user’s profile name. Reported examples:

    • A Flow that branches on the record owner’s profile name.
    • A validation rule that compares profiles.
    • Apex that queries User.Profile.Name for someone other than the running user.
    • Reports and formula fields that display the profile of another user.
    • Managed packages that route by profile. Ask the vendor.

    Salesforce Dictionary adds that the failure is partial: automation reading another user’s profile name usually gets a blank value rather than an error. That’s the reason a test run as a system administrator passes. Admins can see everything.

    How do you check before enforcement, or after it?

    Find the references first, then test as a standard user in a sandbox. Salesforce Ben’s preparation steps are a sensible order:

    1. Search your metadata for anything that references another user’s profile name: validation rules, Flows, Apex, reports and formula fields.
    2. In a sandbox, refactor those references, or add View All Profiles as a stopgap.
    3. Enable Profile Filtering in the sandbox and retest.
    4. Deploy to production, enable the setting, and run a final regression test.

    For step 3, use login-as. Salesforce Dictionary’s advice is to walk the critical paths as a standard user, and to repeat the test for each profile if you’ve got several cut-down ones. The reasoning is simple: a sales rep and a service rep may get different results from the same Flow.

    If it’s already enforced in your org and something has gone strange, start with a debug log on a failing record and look at what the profile value actually was. A blank where you expected “Partner Sales” tells you most of what you need. If you would rather hand the search-and-test work to someone senior, release readiness is part of our managed admin service.

    What is the View All Profiles permission, and should you grant it?

    View All Profiles is the permission that lets a user see other profile names. Grant it to the people and processes that genuinely need to see them, such as admins and operations teams. Salesforce Dictionary calls it the “escape hatch” and advises treating it as a fallback, because giving a broad visibility permission to undo a visibility restriction defeats the purpose.

    The same source says users with certain other permissions, such as Customize Application and Manage Users, are also exempt, eight bypass permissions in all, though it names only three. We couldn’t confirm the full list from a primary source, so check the release note. If your admins already hold those, they’re probably fine, which is also why admin testing proves nothing.

    The better fix is usually to stop checking profile names. A Flow that asks “is the owner’s profile Partner Sales” can ask about a custom permission, a field on the user, or a permission set assignment instead. Those are stable when profiles are renamed or cloned.

    What does this say about profiles versus permission sets?

    It says profile names are a weak thing to build logic on, and that Salesforce keeps tightening the profile. Salesforce Ben reports a Salesforce statement that the Spring ’26 end-of-life for permissions on profiles is no longer enforced, while still recommending a permission set-led model. The article’s date is unclear, so treat the exact timeline as unconfirmed.

    A reasonable direction, offered as opinion: keep profiles minimal, put permissions in permission sets and groups, and make automation depend on what a person can do, not what their profile is called. Then a profile rename, a clone or this release update changes nothing about your logic. If you want to see where permissions come from in your org, a user access review is the natural next job.

    What to do Monday:

    1. Open Setup > Release Updates and note the status and date of Enable Profile Filtering.

    2. Search Flows, validation rules, formula fields and Apex for “Profile.Name” and “$Profile”.

    3. In a sandbox, log in as a standard user from each major profile and run the three processes that depend on profile checks.

    4. Decide who gets View All Profiles, and give it through a permission set, not a profile.

    Where we come in

    Watchbill, by GTM Cloud, is pre-release and isn’t publicly listed yet. Today it shows what each person can do and which profile, permission set or group grants it, and compares two users or sets. That helps with the permission side of this clean-up. It doesn’t scan your Flows or Apex for profile names, and version 1 changes no access. Join the Watchbill pilot if untangling profiles is next.

    Questions people ask

    Do I need to do anything for profile filtering?

    Only if something reads another user’s profile name. Salesforce Ben says admins need to act only if users must see other profiles. Search your Flows, validation rules, Apex and formula fields first. If nothing references another user’s profile name, there’s nothing to fix, but a sandbox test is cheap insurance.

    Will profile filtering break my Flows?

    It can. A Flow that checks the owner’s profile name may get a blank value as a user without View All Profiles, and it fails quietly rather than with an error. Test the Flow as a standard user. If it branches on profile, rewrite it to use a permission or a user field.

    Can I turn profile filtering off?

    Release updates are enforced on Salesforce’s schedule, and Salesforce can delay, change or cancel them. Once enforced, the release update isn’t a switch you control. Your lever is View All Profiles for the users and processes that need it. Read the update’s status in Setup > Release Updates for your org.

    Sources

  • Field history tracking for the User object: what it covers and what it doesn’t

    Field history tracking for the User object: what it covers and what it doesn’t

    The short answer: In Winter ’27, Salesforce lets you track up to 20 fields on the User object, including Profile, Role, Is Active and Manager, with old value, new value, who and when. Salesforce Ben’s release roundup calls it generally available, while the Setup toggle still reads Beta. It doesn’t replace Setup Audit Trail or Login History. Those log different things.

    An auditor asks a plain question: “Who moved Dana from Sales Rep to System Administrator, and when?” You open Dana’s user record. The record shows the profile she has now. It has never shown the one she had on Tuesday.

    Until now, answering that meant a custom trigger, a third-party package, or a lot of squinting at Setup Audit Trail. User field history tracking in Salesforce closes part of that gap. Only part, and it helps to know which part before you rely on it.

    Features vary by edition and license. Check the release notes for your org before you rely on any of this.

    What does user field history tracking record?

    It records changes to the User fields you select, with the old value, the new value, a timestamp and the user who made the change. As reported by the Salesforce Break recap of Winter ’27, changes made through the UI, bulk operations, Apex and the API are all captured. You can track a maximum of 20 fields.

    You can’t choose any field. Salesforce Help gives a fixed list: Name, Alias, Company Name, Division, Department, Title, Address, Phone, Extension, Time, Locale, Language, Mobile Phone, Start Day, End Day, Email, Manager, Contact, Is Active, Profile, Role, Username and Delegated Approver. Custom fields with Auto Number, Formula, Rich Text Area and Long Text Area data types aren’t tracked.

    Help also notes tracking applies to internal users only. And the history appears on the user’s access summary page, not in a related list on the User record.

    Is it generally available or still in beta?

    Both labels are in circulation. Salesforce Ben’s Winter ’27 roundup titles the item “Generally Available” and says it is “now generally available”, and a second Salesforce Ben piece says not to be surprised if the UI still shows a beta label. The Setup toggle is named User Field History Tracking (Beta), and Salesforce Help uses that same name.

    So the feature is described as GA while the control is labeled Beta. We can’t resolve that from the outside. Another recap, from Salesforce Break, says it moved from beta in Winter ’26 to GA in Winter ’27. Read the release notes for your org, and test in a sandbox before you build an audit process around it.

    Treat it as available, labeled Beta, and verify in your own org.

    Where do you turn it on?

    Salesforce Ben reports the switch is in Setup, under User Management Settings: enable User Field History Tracking (Beta). Salesforce Help names the setting but doesn’t give a path in the part we read, so confirm the location in your org. The Metadata API reference lists a matching userFieldHistoryTracking setting on UserManagementSettings, which matters if you deploy settings between orgs.

    Then pick the fields:

    1. In Setup, enable User Field History Tracking (Beta).
    2. Choose the fields to track, up to 20. Salesforce Ben says you configure them once the setting is on. Salesforce Break describes the route as Object Manager, User, Fields & Relationships.
    3. Open a user’s access summary page to read the history.

    Per Salesforce Help, if you turn the setting off and on again, the fields you selected stay selected, and changes made while it was on stay recorded. Tracking is not retroactive: changes before you switch it on aren’t there.

    Which User fields are worth tracking?

    Start with the four that change what a person can do or who they answer to: Profile, Role, Is Active and Manager. That is opinion, but it is easy to defend.

    FieldWhy track it
    ProfileThe biggest lever on what a user can do. The question “when did this person become an admin?” is answered here
    RoleChanges what record access they inherit through the hierarchy
    Is ActiveShows when someone was frozen out or switched back on, which matters at leaver time
    ManagerDrives approval routing and escalation in many orgs, and nobody remembers changing it
    Username, EmailIdentity fields. A changed email on an active user is worth a look. Email is available for tracking only after it has been verified, per Help
    Delegated ApproverQuietly reroutes approvals

    Leave Locale, Language and Title for later. You have 20 slots and no reason to fill them on day one.

    What does it not replace?

    It doesn’t replace Setup Audit Trail, Login History or a user access review, because each answers a different question.

    • Setup Audit Trail logs admin and configuration activity, such as profile and permission changes, per Salesforce Help. Salesforce keeps a limited history and recommends exporting the trail every six months. Winter ’27 also adds a dedicated View Setup Audit Trail permission, as reported by Salesforce Ben, which we cover in the post on that permission.
    • Login History shows who logged in, when and from where. Salesforce Help says the page shows up to 20,000 records from the past six months, with CSV and GZIP downloads for more.
    • Permission set assignments aren’t on the list of trackable User fields. If your question is “who was given this permission set?”, field history on the User object won’t answer it.
    • Role assignments on the Roles Setup page aren’t tracked, according to Salesforce Help. If you change roles that way, field history won’t see it. That is a gap you should know about before an auditor finds it.

    Native history also has a retention limit. Salesforce Help’s general rule is about 18 months in the UI, and the User section we read doesn’t state a different figure, so confirm it for this object. If you need to know who has access today and why, as opposed to what changed, see our post on how to run a user access review in Salesforce.

    What to do Monday:

    1. In a sandbox, find User Field History Tracking (Beta) under User Management Settings and switch it on.

    2. Select Profile, Role, Is Active and Manager, plus Username and Delegated Approver if you use them.

    3. Change a test user’s profile, then open their access summary page and confirm you can read the old value, new value and who changed it.

    4. Diary a six-month reminder to export Setup Audit Trail and Login History.

    Where we come in

    Native User history is good for the 20 fields it allows. For other objects where you need more fields or longer retention, Wake, by GTM Cloud, is in early access: it logs changes to fields you choose and keeps them for as long as you decide, beside Salesforce’s own history. Its page doesn’t describe User object support, so ask before assuming. Details are on the Wake page.

    Questions people ask

    How many fields can you track on the User object?

    Up to 20, chosen from a fixed list that includes Profile, Role, Manager, Is Active, Email and Username, per Salesforce Help. Custom User fields of types Auto Number, Formula, Rich Text Area and Long Text Area can’t be tracked. Tracking covers internal users only.

    Is user field history tracking generally available?

    Salesforce Ben reports it as generally available in Winter ’27, yet the Setup setting and the Salesforce Help page still call it User Field History Tracking (Beta). The sources describe it differently, so check the release notes for your edition and test it in a sandbox before relying on it.

    Does it show who gave someone a permission set?

    No. Permission set assignments aren’t among the User fields Salesforce lets you track. Setup Audit Trail logs admin changes such as permission changes, so start there. Salesforce keeps only a limited history natively, so export it regularly, store the copy somewhere safe, and keep a note of who owns that job.

    Sources

  • The new View Setup Audit Trail permission, and why your auditor will like it

    The new View Setup Audit Trail permission, and why your auditor will like it

    The short answer: Salesforce is adding a dedicated View Setup Audit Trail permission as a release update. Instead of giving an auditor View Setup and Configuration, which opens most of Setup, you grant only this one. Existing access is preserved when it’s enforced. It shows setup changes for 180 days, and it does not record changes to your data.

    The auditor’s email asks for “evidence of who changed the sharing settings this year.” You’re happy to help. The only way to let her read the audit trail has been View Setup, and View Setup lets her read your whole configuration: every profile, every integration setting, every permission set. So you do what most admins do. You log in, download the CSV yourself, and email it. Then she asks for it again next quarter.

    Features vary by edition and license. Check the release notes for your org before you rely on any of this.

    What is the View Setup Audit Trail permission?

    It’s a new, separate permission that controls access to the Setup Audit Trail. Per Salesforce Ben, users no longer need the broader View Setup permission to read it. It’s a release update, and Salesforce Ben says existing users keep their access automatically.

    The case for it is least privilege. The current requirement, View Setup and Configuration, also lets people view the rest of Setup, as Salesforce Ben’s Spring ’27 preview puts it. An auditor, a compliance analyst or a security lead who needs the log gets the log and nothing else.

    When does it take effect?

    Sources disagree, so check the Release Updates screen in your org. Salesforce Ben lists the update in its Winter ’27 admin features. Salesforce Break says it’s enforced in Spring ’27, and a second Salesforce Ben article says enforcement starts in January 2027. Salesforce can also delay, change or cancel updates.

    What both describe about the switchover is the same. At enforcement, any profile or permission set that already has View Setup and Configuration also gets View Setup Audit Trail, so nobody loses access. New profiles, permission sets and users get it only if you assign it. Your Salesforce Trust page gives your instance’s date.

    How do you give an auditor read access without View Setup?

    Create a permission set that contains only View Setup Audit Trail, and assign it to the auditor. Salesforce Ben recommends granting it on its own for audit-trail-only access and using permission sets or permission set groups rather than profiles where you can.

    1. Setup > Permission Sets > New. Name it for what it does, such as “Setup audit trail reader”.
    2. Under System Permissions, select View Setup Audit Trail and save. The permission should appear once the release update is active in your org. We haven’t confirmed its exact location in that list, so check there first.
    3. Assign it to the auditor’s user, ideally for a set period, and note the date in your change log.
    4. Test it: log in as a similar user in a sandbox and confirm the audit trail opens and the rest of Setup doesn’t.

    An auditor with no Salesforce license can’t use any of this. They need a user. That’s one more reason many admins keep sending CSVs, and it’s fine to keep doing it if the audit is a one-off.

    What does the Setup Audit Trail record, and for how long?

    It records configuration changes: who changed what in Setup, and when. According to Salesforce Help, the page lists the date, the user and what the change was, shows the 20 most recent changes on screen, and lets you download the past 180 days. After 180 days, setup entries are deleted.

    Per Salesforce Ben, the log covers things like permission and permission set changes, user assignments, object and field changes, sharing defaults, Flow and Apex class changes, and Login-As use. The detail varies. For page layouts you may see only that a change happened. Sharing rules aren’t itemized, though org-wide default changes are. Apex shows that a class changed, not the code, so it doesn’t replace version control.

    The developer documentation also describes a SetupAuditTrail object you can query through the API, which is how you’d copy entries somewhere durable before the 180 days run out. Gearset’s guide reports that exports are held for 72 hours in the Audit Trail Export Dashboard, so download and file them straight away.

    What does the audit trail not cover?

    It logs setup changes, not data changes. If the question is “who changed the amount on this opportunity,” the audit trail has nothing. That job belongs to Field History Tracking, which covers up to 20 fields per object and has to be turned on field by field. Gearset reports retention of about 18 months in the UI, or 24 through the API.

    It also isn’t a record of what people viewed, exported or ran. Per Gearset’s guide, individual report exports and detailed user activity need Event Monitoring. And it can’t tell you who could do something, only who changed the settings. Three questions, three sources: the audit trail answers who changed the setup, field history answers who changed the data, and a user access review answers who is allowed to do what today.

    What to do Monday:

    1. Open Setup > Release Updates and read the View Setup Audit Trail entry and its date.

    2. Count who holds View Setup and Configuration, then ask each group whether they need it or only need the log.

    3. Build the “Setup audit trail reader” permission set now, so it’s ready.

    4. Put a recurring reminder in your calendar to export the trail before 180 days pass.

    Where we come in

    Watchbill, by GTM Cloud, is pre-release and isn’t publicly listed yet. Today it shows what each person can do and which profile or permission set grants it, and compares two users or sets side by side. It also keeps snapshots and a change history and runs review campaigns. It reads access and changes none, and it isn’t a replacement for the Setup Audit Trail. Join the Watchbill pilot if access reviews are your headache.

    Questions people ask

    Can anyone see the Setup Audit Trail today?

    Per Salesforce Help and Salesforce Ben, users need the View Setup and Configuration permission. Older guides say system administrators only, but the permission is what controls it. After enforcement of the release update, View Setup Audit Trail becomes the dedicated permission, and existing View Setup holders get it automatically.

    Does the Setup Audit Trail log data changes?

    No. It logs configuration changes such as permissions, fields and Flows. Changes to record values are the job of Field History Tracking, with its 20-field limit per object, or of an extension that keeps longer history. Wake, by GTM Cloud, is one, in early access. For activity like report exports, you need Event Monitoring.

    How long does Salesforce keep the Setup Audit Trail?

    Salesforce Help says the downloadable history covers 180 days, after which entries are deleted, and that the page shows only the last 20. If an auditor needs a full year, you have to export on a schedule and keep the files yourself.

    Sources

  • Salesforce Winter ’27 release notes: the changes admins should care about

    Salesforce Winter ’27 release notes: the changes admins should care about

    The short answer: Four Winter ’27 changes need action: Profile Filtering is enforced, tokens and OAuth flows are tightening, SOAP login() needs a permission, and a View Setup Audit Trail permission is on its way. Four more are worth switching on when you’re ready. The remaining items, mostly AI and security features, are good to know about before someone asks.

    The release notes are hundreds of pages long, and Winter ’27 has already reached production orgs. Salesforce’s own schedule had waves from early September to early October, as reported by Salesforce Dictionary. The risk is rarely the headline feature. It’s the quiet one: a Flow that suddenly sees a blank profile name, an integration that stops logging in on a Monday. So this is the shortlist we’d read first, in the order we’d act on it.

    Features vary by edition and license. Check the release notes for your org before you rely on any of this.

    Which Winter ’27 changes need action before anything else?

    Four changes can break something that works today, so read these first. Each has a status, because Salesforce changes dates more often than people remember.

    Profile Filtering (release update, enforced in Winter ’27). Users see only their own profile name unless they hold View All Profiles, according to Salesforce Ben. It was added in Summer ’26. Any Flow, validation rule or Apex that reads another user’s profile name can quietly stop working. We cover the checks in profile filtering is enforced in Winter ’27.

    View Setup Audit Trail permission (release update). Access to the Setup Audit Trail gets its own permission, so an auditor no longer needs the broader View Setup. Existing access is preserved. Sources disagree on timing: Salesforce Ben lists it in the Winter ’27 notes, while Salesforce Break and a second Salesforce Ben article report enforcement in Spring ’27, from January 2027. The detail is in the View Setup Audit Trail post.

    Refresh tokens and OAuth flows (release updates, dated). Per Salesforce’s architect highlights, production refresh tokens expire after 30 days of inactivity from November 4, 2026. The OAuth 2.0 device flow is restricted from November 30, 2026. The username-password, user-agent and hybrid user-agent flows retire on February 20, 2027. A quarterly integration that logs in once every 90 days is the one that gets caught.

    SOAP API login() (release update, as reported). Salesforce Dictionary reports that Winter ’27 enforces the PermissionsUseAnyApiAuth permission for SOAP login() calls, and that users without it get an error instead of a session. We found no primary source we could open for this one, so confirm it in Setup > Release Updates.

    Which Winter ’27 features are worth turning on?

    Four items are optional and off by default, so you choose the moment.

    Keep Manual Shares When Transferring Records. Setup > Sharing Settings > Edit. When on, manual shares survive an owner change, for all records, with no per-record control. Salesforce’s architect post advises checking which processes rely on owner changes to remove access first. Our walk-through: manual shares and owner changes.

    User Field History Tracking. Salesforce Ben reports it as generally available, with up to 20 fields on the User object. The Setup toggle (User Management Settings) still reads “(Beta)”, so the label and the status don’t match. Worth enabling for the fields people ask “who changed that?” about, such as Profile, Role and IsActive. See what user field history covers.

    Flexible inline editing in list views. Two optional settings under User Interface in Setup: one removes the dependence on page layouts, so users can edit any field they have access to. The other allows inline edits in list views with multiple record types. Turn on the first and you’ve changed who can edit what from a list, so test it against field-level security you thought was belt and braces.

    Setup with Agentforce enhancements. Salesforce’s blog lists these as generally available. Per Salesforce Ben, they include managing Dynamic Actions on mobile and creating related list enrichments by describing what you want. Treat the output like any other change: look at it in a sandbox before production.

    What else is in Winter ’27 that is good to know?

    Several items are more about being able to answer a question than doing a task. The status matters more here than anywhere.

    • MCP Risk Scores in Security Center (GA). Each third-party MCP server gets a Low, Medium or High rating, scanned at registration and monitored afterward, per Salesforce’s blog of October 13, 2026. Admins can block high-risk servers. Relevant if anyone in your org has connected an agent to something outside Salesforce. More in MCP risk scores in Security Center.
    • Observability Center (beta). A single console for tracing agent sessions and errors. Beta, so no production dependencies yet.
    • Lifecycle Center (GA). The new name for DevOps Center, with approvals and audit logging for agent-generated code.
    • Preview records from Lightning reports (beta). The eye icon opens a record in a sidebar without leaving the report.
    • SOQL FORMULA() in WHERE (beta). Sandboxes, Developer Editions and scratch orgs on API 68.0 or later. Not available in production.

    How do release updates and dates actually work?

    Release updates are dated by Salesforce, but the dates move. Setup > Release Updates shows what applies to your org and, where there’s a Test Run, lets you try it first. The date for your instance is the one published on Salesforce Trust.

    Two examples from this cycle. Salesforce Dictionary reports the OAuth username-password retirement moved out of Winter ’27 to February 20, 2027, and that an email-domain update was cancelled and replaced by another with a December 1, 2026 date. Check the live screen, not a blog post from August, this one included.

    How do you check a release against your own org?

    Search your metadata for what the release touches, then test in a sandbox as a person who isn’t you. A system administrator passes tests that a sales rep fails.

    1. Open Setup > Release Updates and list everything marked as enforced or upcoming.
    2. For each, search Flows, validation rules, formula fields, Apex and reports for the thing it changes.
    3. Use login-as on a standard-user profile in a sandbox that has the update on.
    4. Ask the vendor of any managed package whether it’s ready.
    5. Write the result down, even if the result is “nothing found.” Next release you’ll want it.

    What to do Monday:

    1. Open Setup > Release Updates and screenshot the list with its dates.

    2. Search your Flows and validation rules for references to another user’s profile name.

    3. List every integration that hasn’t logged in for 30 days, and check its refresh token.

    4. Count who holds View Setup, and decide who really needs it.

    Where we come in

    Reading release notes against a real org is a few hours three times a year, and it’s exactly what slips when the backlog is long. We write up what changed and what to do about it in The Fix, our newsletter for admins. It doesn’t read your org for you, and it won’t replace a sandbox test, but it tells you which pages to open.

    Questions people ask

    When was Winter ’27 released?

    Salesforce rolled Winter ’27 out to production in waves. Salesforce Dictionary reports September 4, October 2 and October 9, 2026, with the date for your instance on Salesforce Trust governing your org. Sandbox preview came earlier. By now, your org has very likely upgraded.

    Are the Winter ’27 features all generally available?

    No. Salesforce’s blog says its platform features are generally available unless noted, and marks Observability Center as beta. Salesforce Ben lists report record preview and SOQL FORMULA() as beta too, and User Field History Tracking as generally available despite a Setup label that says Beta. Check each release note.

    Can you delay a release update?

    Sometimes. Salesforce publishes an enforcement date for each, and most have a Test Run or a way to enable them early. Once enforced, you generally can’t opt out. Salesforce may also delay, change or cancel an update, so recheck the dates in Setup before you plan around them.

    Sources