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