Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Spring '26 overview
For Admins

Spring '26

Spring '26 is the Agentic Enterprise release. The biggest admin-facing news is Setup with Agentforce (Beta) — an in-Setup AI assistant that creates objects, manages user access, builds flows, and answers org-health questions through natural-language chat. Most Salesforce clouds are renaming, too: Sales Cloud → Agentforce Sales, Service Cloud → Agentforce Service, Field Service → Agentforce Field Service. The functionality is unchanged but the product names you see in Setup, docs, and licensing will shift.

What's new for admins

  • Setup with Agentforce (Beta). A conversational agent inside Setup that can create custom objects and fields, manage queues, troubleshoot user access from the Setup Audit Trail, generate and open flows directly in Flow Builder, and surface org-health metrics like Security Health Check score, Apex health, and login errors. Beta in 12 languages now (Catalan, Danish, Dutch, Finnish, French, German, Italian, Japanese, Norwegian, Portuguese, Spanish, Swedish). Requires the Use Setup with Agentforce and Execute Prompt Templates (or Customize Application) permissions.
  • Email-domain verification is now mandatory. Salesforce no longer delivers email from unverified sending domains. After Spring '26 patch 11, every domain you send from must be verified by an active DKIM key or via the Authorized Email Domains list. New domains added after Feb 25, 2026 require verification immediately; sandboxes enforce on Apr 14, 2026 and production on May 4, 2026. Enable Use a substitute email address for unverified domains on the Deliverability Setup page to soften the cutover.
  • Three WCAG 2.2 accessibility Release Updates. Enable enhancements for page headers and modal windows, then for cards/docked containers/menu lists/panels, then for date pickers/popovers/bottom utility bars/record headers. The first update is a prerequisite for the other two — turn it on first in your sandbox.
  • Backup & Recover Next is now a native app. Daily automated backups, restore by record, with a refreshed UI and automatic region detection — all inside your org.
  • Privacy Requests in Privacy Center fulfill Right to Be Forgotten requests. You can now ignore object processing errors, bypass automations at the object or policy level, and customize batch sizes for privacy jobs.
  • Connected app creation is disabled by default for all new orgs. Use External Client Apps instead. Existing connected apps continue to work, but plan a migration path. Same applies to SAML-enabled connected apps.
  • Archive App lets you autoarchive old or inactive data so production performance stays clean while you keep the historical records reachable.
  • Salesforce Foundations picks up Email Builder Lite for batch sends to Sales contacts and leads, audience-segment definition from Lead and Contact list views, and Tableau dashboards in the Marketing app.

What's deprecated

  • Salesforce for Outlook retires in December 2027 — start moving teams to the Outlook Integration plus Einstein Activity Capture.
  • Open CTI is scheduled for retirement (replaced by Service Cloud Voice integrations).
  • Legacy Chat is being retired — migrate to Enhanced Chat / Messaging.
  • Microsoft Exchange Web Services (EWS) retirement affects Lightning Sync, the Outlook Integration, and any other email-related feature that uses EWS — coordinate with your Exchange admin.
  • Legacy host name redirections end in Spring '26 (the Update References to Legacy Host Names Release Update is now enforced). Update any hard-coded legacy URLs in integrations, custom code, and email templates to your My Domain URL.

What's still in beta

  • Setup with Agentforce — beta as above; pilot for Salesforce mobile-app build-out.
  • Clean Up Messaging Session List Views without Disrupting Conversation History.
  • Voicemail Drop for Outbound Calls.
  • Database Encryption is GA in all regions (was beta in some), and Data Detect now scans 100 objects and unlimited fields with Field Audit Trail going from 60 to 200 fields.

Want a deeper read on any one feature? Use the dictionary cross-links below — every term listed has a full definition page on this site.

What to test in your sandbox

  1. 1. Verify every email-sending domain via DKIM

    In Setup → Email → Deliverability → DKIM Keys, generate or import a DKIM key for every domain that appears as a from-address in your org (org-wide email addresses, user emails, workflow alerts, flow emails, lead-routing notifications). Domains added after Feb 25, 2026 must be verified immediately. Turn on *Use a substitute email address for unverified domains* on the Deliverability page as a cutover safety net.

    Reference: dkim-keys, authorized-email-domains, deliverability

  2. 2. Pilot Setup with Agentforce in a sandbox

    Refresh a Developer or Partial Copy sandbox after sandbox preview (Jan 9, 2026), then enable Setup with Agentforce in your dev org. Assign yourself the *Use Setup with Agentforce* permission plus either *Execute Prompt Templates* or *Customize Application*, then chat with the agent to create an object, add a queue, and ask "Why can't [user] manage users anymore?" to see the Setup Audit Trail troubleshooting flow.

    Reference: setup-with-agentforce-beta, permission-set, view-setup-audit-trail

  3. 3. Activate the three WCAG 2.2 Release Updates in order

    In Setup → Release Updates, enable *Enable Accessibility Enhancements for Page Headers and Modal Windows* first — it's a prerequisite for the other two. Then enable the cards/docked-containers/menu-lists update and the date-pickers/popovers update. Test custom Visualforce pages, embedded LWCs, and any third-party AppExchange components at 200%+ zoom before activating in production.

    Reference: lightning-components, visualforce

  4. 4. Audit connected apps, plan ECA migration

    Connected app creation is disabled by default in new orgs and SAML connected apps must migrate to External Client Apps. From Setup → Manage Connected Apps, list every connected app, identify the ones used for SSO/SAML, and schedule a migration to ECA. Test in a sandbox first — the OAuth flows and consumer keys differ.

    Reference: connected-app, external-client-app-manager, oauth

  5. 5. Enable Backup & Recover Next as the native app

    Contact your AE for the license, then enable Backup & Recover Next from Setup. Configure your daily backup schedule and run a restore drill against a single test record to confirm the recovery path works end-to-end before you rely on it. Available on a rolling basis starting Spring '26 in GovCloud and Japan first.

  6. 6. Try Privacy Requests for Right to Be Forgotten

    In Privacy Center, set up a Privacy Request to fulfill RTBF for one test contact. Verify the policies bypass any automations you've marked as exempt, and check that batch size tuning behaves as expected on a sandbox before you point it at production data.

    Reference: privacy-center

  7. 7. Replace any legacy host names in integrations

    The *Update References to Legacy Host Names* Release Update is enforced in Spring '26 — redirections end. Search outgoing integrations, email-template merge fields, custom Apex callouts, and any external systems for hard-coded *.salesforce.com* legacy patterns and switch them to your My Domain URL. Run the Hyperforce Assistant if you haven't migrated yet.

    Reference: my-domain, hyperforce-assistant

  8. 8. Try Archive App on a low-risk object

    Pick a high-volume object you no longer report on (Activities older than 5 years, closed Cases past retention) and run Archive App against it in a Full sandbox. Confirm the archived data is reachable from the Archive App UI and that your reports/list views still render in acceptable time. Then schedule autoarchive policies in production.

    Reference: full-sandbox

Related dictionary terms

See Developers take →See Architects take →See Consultants take →