Key Updates for Permissions, Access & User Management
The Salesforce Spring ’25 release introduces several important enhancements for administrators responsible for permissions, access, governance, and org security. Below is a clear breakdown of what’s new and why it matters.
1. New “View All Fields” Permission + Renamed Object-Level Permissions
View All Fields Permission
Spring ’25 introduces a new permission that allows users to read every field on a standard or custom object — including fields added in the future. This makes it simpler to grant complete read visibility without exposing edit rights.
Renaming of Existing Object-Level Permissions
To reduce confusion, Salesforce has renamed two well-known permissions:
- View All → View All Records
- Modify All → Modify All Records
The functionality remains the same, but the naming now better reflects that these permissions apply to records, not fields.
Why it matters:
- Clarifies the difference between field- and record-level access
- Reduces audit and documentation confusion
- Supports a cleaner, more accurate permissions model
- Simplifies granting full field visibility where appropriate
2. Improved Permission Set Management
Spring ’25 includes enhancements that make permission sets easier to manage and maintain.
- Admins can now remove user permissions and custom permissions directly from the Permission Set Summary page
- Included permissions within a Permission Set Group can be viewed and more easily managed
- Summary pages provide clearer insight into what a permission set or group actually grants
Why it matters:
- Faster cleanup of large or legacy permission sets
- Easier documentation and governance
- Fewer clicks when auditing or updating access
- Better alignment between assigned permissions and actual user needs
3. Enhanced User & Role List Views
User and Role list views have been upgraded to provide:
- Faster load times
- More supported fields
- Improved inline editing
- Better sorting and filtering options
These improvements streamline high-volume user administration, especially for organisations with large user populations.
Why it matters:
- Easier management of user access at scale
- Less time spent navigating to individual user pages
- Cleaner experience for user onboarding and offboarding
- More efficient access reviews
4. Continued Enhancements to User Access Policies
Spring ’25 continues Salesforce’s multi-release push toward simplified user access management, including:
- Clearer visualisation of permission-set group assignments
- Improved tools for assessing what access a user has and why
- Better support for job-function-based access models
Why it matters:
- Strengthens governance and compliance documentation
- Helps reduce profile reliance in favour of permission sets and groups
- Supports a more maintainable, scalable access model
- Improves auditability of user permissions
5. Security, Identity & Access Flow Updates
A few important identity-related updates also impact access management:
Customisable Welcome Emails
Admins can now customise the welcome email for new users, including setting verification-link expiry (1 day, 7 days, or 180 days).
Updated Password Reset Flow
When users reset their password, they must now authenticate using their chosen MFA method, increasing security during the process.
Why it matters:
- Strengthens identity verification
- Reduces risk during onboarding and password resets
- Supports compliance and security-first access models
Final Thoughts
Spring ’25 delivers practical and impactful improvements for anyone managing permissions, access, security or governance within Salesforce. These enhancements:
- Improve clarity around object and field access
- Streamline permission-set and group maintenance
- Modernise user and role administration
- Strengthen identity and authentication processes
For teams using the Security & Access Manager Suite — including modules for object access, field access, record access and permissions management — these updates complement core capabilities and support stronger, more transparent access governance.