Salesforce Winter ’27 Admin Checklist: 14 Features to Review Before Your Upgrade

salesforce admin checklist
⏱ 4 min read
SALESFORCE RELEASE GUIDE · WINTER ’27

Salesforce Winter ’27 brings changes to Agentforce enablement, reporting, security, list views, field history tracking, and Flow Builder. Use this practical admin checklist to review the most important updates, identify potential risks, and prepare your Salesforce org before rolling out new capabilities.

14 Feature Areas
10-Minute Admin Checklist
Agentforce Readiness

THE QUICK ANSWER
Contents hide

What Should Salesforce Admins Check Before Winter ’27?

Start by confirming your org’s release schedule, reviewing Agentforce enablement, auditing AI permissions, checking existing agents, and understanding your applicable licensing and credit arrangements. Then assess the Winter ’27 changes affecting reporting, sharing, user access, field history, SOQL, and automation.

Remember: enabling the Agentforce platform does not automatically deploy or activate an agent. Configuration, permissions, channel setup, testing, and appropriate governance remain essential.

IMPORTANT PRE-UPGRADE CHECK

Agentforce Is Enabled by Default in Winter ’27: What Admins Need to Know

Salesforce has announced default enablement of the Agentforce platform for eligible orgs through a rolling rollout. The Agentforce platform toggle is also removed from its previous Setup location.

The important distinction: Platform enablement does not automatically deploy an autonomous agent. Agents still require configuration and activation, while customer-facing interactions depend on the relevant channel and deployment setup.

Admin takeaway: Review AI agent permissions, sensitive data access, ownership, and approval processes before introducing agents into business-critical workflows.

What Changes, and What Stays Under Admin Control?

  • Platform access: Eligible orgs may have Agentforce enabled by default.
  • Einstein Setup: The Einstein generative AI setting remains relevant to the configured AI experience. Review its current state and dependencies.
  • Agent activation: Agents still require configuration and activation.
  • Permissions: Restrict Manage AI Agents to authorized users.
  • Billing: Platform enablement alone should not be treated as confirmation of additional charges or zero cost. Verify your contract, usage model, and licensing terms.

14 Salesforce Winter ’27 Features Admins Should Review

Use the following feature-by-feature guide to determine what matters to your org, what needs testing, and where you may need to update permissions, configuration, or internal processes.

01 · REPORTING

Preview Records from Lightning Reports Without Losing Context (Beta)

Users can preview records in a sidebar without leaving Lightning reports. Select the eye icon and choose a record to inspect its details while retaining the current report context.

Admin action: Test record access, preview behavior, and compatibility with frequently used reports. Confirm beta availability before training users.
Salesforce Winter '27 Lightning report record preview

02 · EXPERIENCE CLOUD

Embed Lightning Reports in LWR Experience Cloud Sites (Beta)

Admins can embed Lightning reports in eligible Lightning Web Runtime (LWR) Experience Cloud sites. Enable the feature in Setup, then add the Lightning Report component through Experience Builder and configure the report ID.

Admin action: Validate site access, report visibility, sharing, and portal user permissions.
Embedding Salesforce Lightning reports in Experience Cloud

03 · EXPERIENCE CLOUD

Embed Lightning Dashboards in LWR Experience Cloud Sites (Beta)

This beta capability lets admins display Lightning dashboards on eligible LWR Experience Cloud pages. Enable the feature, add the Lightning Dashboard component in Experience Builder, and specify the dashboard ID.

Admin action: Test dashboard visibility, permissions, data exposure, and embedded component behavior.
Salesforce Lightning dashboard embedded in Experience Cloud

04 · REPORTING

Show Only Matching Records Across Joined Report Blocks (Beta)

The Common Rows Only option filters joined reports to records appearing across all report blocks. For example, a report combining Accounts and Active Opportunities can focus on accounts with matching active opportunities. Salesforce Customer Support must enable this beta feature.

Admin action: Compare report totals and matching records before sharing results with stakeholders.
Matching records across joined Salesforce report blocks

KIZZY AI READINESS ASSESSMENT

Before You Switch On AI, Check What’s Ready.

Production-ready AI requires trusted data, secure permissions, defined workflows, and measurable outcomes. Assess your organization’s readiness before scaling Agentforce.

Explore the AI Readiness Assessment →

05 · USER EXPERIENCE

Add the Follow Button to the Dynamic Highlights Panel

Admins can display the Follow/Unfollow button in the Dynamic Highlights Panel, allowing users to follow records and receive relevant feed updates. Configure visibility through the panel properties in Lightning App Builder using the Hide Follow/Unfollow button setting.

Admin action: Confirm that record following supports your team’s collaboration and notification needs.

06 · RECORD SHARING

Keep Manual Shares When Transferring Records

The Keep Manual Shares When Transferring Records setting lets admins preserve manual shares during ownership changes. Find it under Setup → Sharing Settings. It is off by default and can affect access across the org.

Security consideration: Test ownership transfers to ensure retained shares do not grant unintended access.

07 · SECURITY

Enforce Profile Filtering

The profile-filtering release update introduced in Summer ’26 is enforced in Winter ’27. It restricts users from viewing other users’ profiles unless they have the required permission, such as View All Profiles.

Admin action: Check integrations, support procedures, and administrative workflows that require cross-profile visibility.

08 · ADMINISTRATIVE SECURITY

Use a Dedicated Permission for Setup Audit Trail

A dedicated View Setup Audit Trail permission lets admins grant audit-trail access without automatically granting the broader View Setup permission. Existing access is preserved according to the release guidance.

Admin action: Review permission assignments and grant audit access through appropriate profiles or permission sets.

09 · LIST VIEWS

Make Inline Editing in List Views More Flexible

Two optional User Interface Settings improve list-view inline editing:

  • Remove list view inline edit dependencies on page layout: Allows editing fields users can access even when those fields are absent from the page layout.
  • Make inline edits in list views with multiple record types: Supports inline editing across records with different record types.

Both settings are off by default and can be configured under Setup → User Interface Settings.

Admin action: Test field permissions, validation rules, record types, and editing behavior.

10 · AUDITABILITY

Track Field History on the User Object

User Field History Tracking adds visibility into selected User object field changes. The supplied release guidance indicates support for tracking up to 20 fields. Confirm supported fields and retention requirements before relying on this capability for compliance.

Admin action: Identify user-account changes relevant to security reviews and audit requirements.

11 · DEVELOPER EXPERIENCE

Compare Field Values in SOQL with FORMULA() (Beta)

The beta SOQL FORMULA() enhancement supports formula-based comparisons in WHERE clauses for selected query scenarios, potentially reducing the need for additional formula fields. The supplied guidance identifies sandbox, Developer Edition, and scratch-org support with API version 68.0 or later, rather than production.

Developer note: Verify API-version and environment restrictions before using this beta feature.

12 · AGENTFORCE

Configure Salesforce More Easily with Agentforce

Setup With Agentforce offers natural-language assistance for selected configuration tasks, including managing mobile Dynamic Actions and creating related-list enrichments. Admins can describe changes, answer clarification questions, and review proposed configurations. Org Health and Usage metrics can also be favorited or hidden.

Admin action: Review AI-proposed changes, validate permissions, and follow change-management procedures before deployment.

13 · FLOW BUILDER

Improve Flow Builder Testing, Debugging, and Maintenance

Flow Builder improvements include richer version comparisons, edit history, element grouping, unused-resource visibility, reusable test scenarios, beta mock outputs for actions and subflows, and better required-field validation. These capabilities can simplify automation maintenance and troubleshooting.

Admin action: Test critical flows in a sandbox, focusing on permissions, user context, fault paths, sharing, and record locking.

14 · SCREEN FLOWS & AUTOMATION

Extend Automation with Screen Flows and New Components

Winter ’27 expands screen flows for selected-record actions from list views and related lists. A native Time component and additional testing and debugging improvements can help teams build guided workflows with less custom development.

Admin action: Evaluate relevant use cases and verify component availability before redesigning existing workflows.
Salesforce Winter '27 screen flow enhancements

FOR ENTERPRISE AI TEAMS

Move Beyond AI Pilots. Build for Production.

Production-ready enterprise AI requires reliable data, secure integrations, measurable outcomes, and collaboration between engineering and business teams. Discover how Forward Deployed Engineering connects AI strategy with practical implementation.

Explore the FDE Approach →

YOUR PRE-UPGRADE ACTION PLAN

The Ten-Minute Salesforce Winter ’27 Admin Checklist

Run through these seven checks to understand your org’s Agentforce readiness, identify permission gaps, and make a deliberate adoption decision before the rollout becomes another last-minute admin task.

Your 7-Point Admin Checklist

  • 01
    Confirm your rollout date.
    Check whether your Salesforce edition is in scope and verify your org’s actual enablement date through Salesforce Trust under the Maintenance tab.
  • 02
    Record your current Einstein AI settings.
    Document the current state of the Einstein generative AI setting and identify existing features, workflows, or integrations that depend on it.
  • 03
    Audit Manage AI Agents permissions.
    Inventory users with the Manage AI Agents permission and restrict access to authorized builders who genuinely need it.
  • 04
    Inventory existing Agentforce agents.
    Separate created agents from activated agents, identify their owners, and document the channels connected to every active agent.
  • 05
    Document your Agentforce credit model.
    For applicable consumption-based pricing, record the stated rates of 20 credits per action in production and 16 in sandbox. Confirm that credits do not roll over and account for monthly arrears billing for overages. Verify the rates and billing terms against your contract.
  • 06
    Verify unmetered user assignments.
    If your contract includes unmetered usage, check that the Unmetered User-Based AI permission is assigned to the correct users and matches your contractual entitlements.
  • 07
    Make a deliberate adoption decision.
    Decide whether your organization will adopt Agentforce this quarter or defer adoption. Document the decision, accountable owner, and next review date.

Need Help Preparing Your Org?

If your inventory uncovers agents without clear ownership, excessive permissions, or missing governance controls, Kizzy Consulting can help you establish a structured approach before more builders arrive.

Discuss Your Agentforce Readiness →

WINTER ’27 ADMIN GUIDE

Frequently Asked Questions

What are the main Salesforce Winter ’27 features?

Highlights include report previews, LWR report and dashboard embedding, joined-report filtering, flexible list editing, sharing improvements, stronger permissions, User field history tracking, SOQL enhancements, Flow Builder updates, and Agentforce-assisted configuration.

Is Agentforce enabled by default in Winter ’27?

Salesforce has announced default platform enablement for eligible orgs through a rolling rollout. Check Salesforce Trust, your org’s release schedule, and the latest official release notes for your eligibility and timing.

Does enabling Agentforce automatically activate customer-facing agents?

No. Agents still require configuration and activation. Customer-facing interactions depend on channel and deployment setup, with appropriate permissions and data-access controls.

What should Salesforce admins check first?

Start with the enablement schedule, Einstein generative AI settings, Manage AI Agents permissions, existing agent ownership and activation, applicable credit terms, and unmetered user assignments. Then test critical workflows, integrations, reporting, and security changes in a sandbox.

KIZZY CONSULTING

Turn Salesforce Winter ’27 Updates Into Business Value

Preparing for a Salesforce release involves more than checking new features. Kizzy Consulting helps teams evaluate Agentforce readiness, strengthen governance, optimize Salesforce configurations, and turn enterprise AI initiatives into practical business outcomes.

Unknown's avatar
Author:
Sanjeet Mahajan is the Founder & CEO of Kizzy Consulting and 13x Salesforce Certified Architect with over a decade of experience in enterprise AI and CRM transformation. He leads a Salesforce Ridge Partner firm that has delivered 120+ projects globally, specialising in agentic AI, automation, and Salesforce implementation. Connect with Sanjeet on LinkedIn: https://www.linkedin.com/in/sanjeet-mahajan-9707689a/

Leave a Reply

Your email address will not be published. Required fields are marked *