CleanForce

No Object should ever be External Public. Not directly. Not indirectly

By , Salesforce CTA·1 min read·First shared on LinkedIn,

Not through a OWD, Sharing Rule, not through "View All" checked on a Profile or Permission Set to save time and not even via Flow/LWC running in system mode.

There should always be a condition, at least on status like Is Active or better something specific.

Removing too broad Public External access is part of every good security cleanup.

Is your Org carrying this kind of dirt?
Book a free 60-minute Salesforce Technical Debt Audit: a score for Usability and Build Quality, and your top cleanup priorities.

More on “Security & licences”

Security & licences · 2 min

You're probably paying $50k to $250k a year for licences nobody uses

Most orgs aren't bleeding money on big strategic decisions. They're bleeding money on the boring stuff nobody checks. License cost optimization is one of the easiest wins in Salesforce, and…

Read field note Security & licences · 1 min

Nobody thinks about the Apps they installed three years ago and forgot

That's the problem, every AppExchange Package sitting in your Org from a project that ended, a trial that never got cleaned up, a vendor relationship that quietly ended, is not neutral. It…

Read field note Security & licences · 1 min

Security cleanup is about deciding what is even in the room

It is about deciding what is even in the room.

Read field note
More: Security & licencesAll field notes