There’s a peculiar phenomenon that appears in almost every mature Salesforce environment.
A sales manager needs visibility into a new territory. An agency contractor joins for a three-month project. A support lead needs elevated permissions to troubleshoot a customer issue. An administrator needs temporary rights to modify workflows. All entirely reasonable requests.
The access gets approved. The project ends. The access remains. Six months later, nobody remembers why it exists. Twelve months later, it’s become one of the longest-serving members of the sales team.
That’s Salesforce access management in a nutshell. Most organizations aren’t struggling to grant access. They’re struggling to remove it.
The identity problem lurking inside Salesforce
Salesforce contains some of the most valuable information in an organization. Customer records. Revenue forecasts. Opportunity pipelines. Support cases. Contracts. Business relationships built over years.
Naturally, we (should) spend a great deal of time deciding who should have access.
We spend considerably less time asking whether they still need it.
The challenge isn’t unique to Salesforce. Across the industry, identity has become one of the most exploited attack paths. According to PAN’s 2026 Global Incident Response Report, weak identity controls contributed to 90% of cyber incidents, and in analyzed cloud identities, 99% had excessive permissions.
Attackers increasingly don’t break in. They log in. They find an account with more access than it should have and start exploring.
That’s why Salesforce access management isn’t simply an administrative exercise. It has to be an ongoing security discipline.
Salesforce is already moving toward least privilege
To Salesforce’s credit, the platform has spent years evolving its access model.
Historically, profiles handled much of a user’s access. Today, Salesforce promotes a permission-set-led model, in which profiles provide baseline settings, while permission sets and permission set groups provide more granular access. The goal is a system that is easier to scale, audit, and maintain. It’s a sensible approach.
Permission sets allow organizations to grant specific capabilities without creating countless custom profiles. Permission set groups make those permissions easier to package and manage.
The problem is that permission sets solve how access is granted. They don’t necessarily solve how long access should remain. That’s where things can become both fiddly and interesting.
The real risk is access drift
Each access decision makes sense in isolation. Collectively, they create an environment where nobody has a complete picture of who has access, why they have it, whether they use it, or whether it should still exist. The result is a growing gap between intended access and actual access. And that gap is where risk lives, and that’s critical to surviving a cyberattack.
Access drift creates waste
There’s another side effect to excessive Salesforce access that’s rarely discussed: cost.
I once worked for a company for 18 months, then while writing a case study, someone from another division said, “It’s all in Salesforce,” and I swear I didn’t even know I had a license assigned to me—apparently, since day one. Crazy, considering a standard Salesforce license costs between $25 and $550 per user, per month, depending on the edition.
Unused licenses, forgotten contractors, dormant or orphaned accounts, and employees who have moved to new roles often continue to consume SaaS resources long after the business need has disappeared. The same visibility problems that make access difficult to govern also make software spending harder to control. When organizations can’t easily see who still needs access and who doesn’t, they often pay for licenses that nobody is actively using. Good Salesforce access management isn’t just a security practice. It’s also a practical way to save on SaaS by reducing waste, improving license utilization, and ensuring spending reflects actual business requirements.
Salesforce access management needs context
The modern identity challenge isn’t about permissions alone. It’s about understanding the context around those permissions. When we look at a Salesforce permission set assignment, several questions immediately emerge:
- Why was this access granted?
- Who approved it?
- Is it still being used?
- Should it expire?
- What happens when the user changes roles?
- Does this access create downstream risk elsewhere?
Those questions become even more pertinent as organizations connect Salesforce to cloud platforms, data warehouses, collaboration tools, AI systems, and third-party applications. The identity landscape no longer exists inside a single directory. It spans the entire business.
Recent research highlights how quickly this complexity is growing. SaaS applications were involved in 23% of incidents investigated last year, up significantly from previous years as attackers increasingly abuse trusted applications, APIs, and connected systems.
The question isn’t merely who can access Salesforce. It’s what that access can ultimately lead to.
From permanent access to purpose-built access
The healthiest Salesforce environments tend to share a common philosophy.
Access should exist because there is a current business need. Not because there was one six months ago. That means making access more visible, more accountable, and more temporary. A contractor receives access for the duration of a project. An administrator receives elevated permissions for a maintenance window. A support engineer receives additional rights while resolving a critical incident.
When the work ends, the access ends too, automatically with just-in-time access. No cleanup ticket. No calendar reminder. No annual audit discovering permissions nobody can explain. Just access aligned with actual need.
This reduces risk, improves governance, simplifies compliance, and makes life considerably easier for the busy people responsible for managing identity.
Nobody wants to explain why a former contractor still has access to customer data eighteen months after leaving. Especially when proving least privilege during an audit.
Salesforce gives organizations powerful tools to manage permissions. The challenge is ensuring access remains aligned with real business needs as people, projects, and responsibilities change.
Trustle helps organizations modernize Salesforce access management by simplifying access requests, approvals, visibility, governance, and time-bound permissions. Instead of accumulating standing access that nobody reviews, teams can grant the right access at the right time and automatically remove it when it’s no longer needed. Start a free Trustle trial today, and in 30 minutes you’ll see how temporary, auditable, least-privilege access can help reduce Salesforce risk while making access management easier for everyone involved.
