Any Salesforce admin who has ever done a field-level security audit knows the process: open a profile, navigate to object settings, find the field, note the access, repeat for every other profile, then repeat for every permission set. It is tedious, error-prone, and nobody does it as often as they should. Summer '26 adds a Field Access tab directly to Object Manager that shows the full picture in one place.
What the Field Access tab shows
At the bottom of each object in Object Manager, a new Field Access tab lists every field on the object alongside a consolidated view of exactly how access is granted — across all profiles and permission sets — in a single interface.
Previously, getting this view required navigating each profile individually, cross-referencing permission sets separately, and building a mental or spreadsheet-based picture of who can see and edit which field. For a mid-sized org with 20 profiles and 40 permission sets, that process takes hours and is almost guaranteed to miss something.
The Field Access tab shows it in one view. One object, every field, all access configurations visible simultaneously.
| Field Label | Profile / Permission Set Access | Granted Via |
|---|---|---|
| Amount | ✓ Read / Edit Sales Rep, Sales Manager | Profile: Sales Rep · Profile: Sales Manager |
| Annual Contract Value | ✓ Read / Edit Finance, Admin 📖 Read only Sales Rep | Perm Set: Finance View · Profile: Admin |
| Internal Deal Notes | ✓ Read / Edit Sales Manager, Admin ✗ No access Sales Rep, Support | Perm Set: Manager Access · Profile: Admin |
| Stripe Subscription ID | 📖 Read only Finance, Admin ✗ No access Sales Rep, Support, CS | Perm Set: Finance View · Profile: Admin |
Why this matters more than it sounds
Field-level security is one of the most common gaps in Salesforce org audits. Orgs grow, permission sets multiply, profiles get copied from other profiles, and nobody has a clear picture of who can read or edit which field. Compliance audits, security reviews, and new admin onboarding all require this visibility — and getting it has always required more effort than it should.
The Field Access tab does not change permissions. It makes the existing permissions visible and auditable at a glance. That distinction matters for compliance contexts specifically: the audit requirement is often to demonstrate that someone reviewed field access, not that they changed it. Summer '26 makes that review faster, more reliable, and easier to document.
Three situations where this saves significant time
What it does not do yet
The Field Access tab is read-only in the initial Summer '26 implementation. You can view field access across all profiles and permission sets, but you cannot edit permissions from this interface. Changes still require navigating to the profile or permission set and making edits there.
Worth watching: The ability to edit permissions from the same view — which would make it genuinely powerful — is the likely Winter '27 addition. The visibility improvement is real and significant now. Editing from the same surface is the logical next step.
Field-level security has always been one of the hardest things to audit in a Salesforce org. Summer '26 does not solve the permissions complexity — it makes it visible. That is the starting point for everything else.
