Sergio Roberto Romanini · Salesforce Administrator · Agentforce Specialist · Barcelona, Spain
In June 2026, I documented how I would solve five core admin challenges at TechFlow Solutions. Security model, Flow automation, Approval process, Data management, Reports and dashboard. Each one built end-to-end, with video walkthrough and full documentation.
I said the answer might look different next month.
The Salesforce Summer '26 release confirmed that. Setup with Agentforce is now generally available, built for admins to configure Salesforce in natural language without leaving the Setup Home. Field Access in Object Manager consolidates field permission visibility into a single auditable view. Flow Builder supports Agentforce-assisted iteration and automated error fixing. Approval processes now support unanimous consent by group. And Salesforce Headless 360, also introduced in Summer '26, positions the admin's configuration work as the trust layer that external systems, apps, and agents depend on.
This project revisits the same five problems with that in mind. Same challenges, same org, different tools. Built in July 2026 by a Salesforce Certified Administrator and Agentforce Specialist.
TechFlow's field-level access for the Annual Revenue field on Account was configured entirely through Profiles. The Support Manager (Service Supervisor profile) had read access granted directly by the Profile, with no Permission Sets involved. While functional, this approach no longer follows Salesforce best practice: Salesforce is actively moving field permissions away from Profiles and into Permission Sets, giving admins more granular and auditable control over who can access sensitive data.
The original solution used OWD, role hierarchy, and Field-Level Security through Profiles. That still works. Two things are different now.
Field Access in Object Manager shows every source of access for a specific field, across Profiles, Permission Sets, and Permission Set Groups, in one consolidated view. And Setup with Agentforce, now GA, lets admins create and manage Permission Sets using natural language from the Setup Home, with no Agentforce credits consumed for Setup actions.
I opened Field Access for the Annual Revenue field to confirm the before state: access coming entirely from the Service Supervisor Profile, no Permission Sets involved.
Field Access (Summer '26): Annual Revenue — before state. Access comes entirely from the Service Supervisor Profile.
I then used Setup with Agentforce to create two Permission Sets via natural language prompts, one at a time: