Salesforce News

Last Updated on April 29, 2026 by Rakesh Gupta The Summer’26 release is already available via the Pre-release and Pre-release for partners programs. Starting May 08, 2026, Sandboxes will be upgraded to give early access to the Summer’26 experience. Salesforce Summer’26 just dropped, and it doubles down on what matters The post Salesforce Summer’26 Release Quick Summary appeared first on Automation Champion.

Recently, many people in the Salesforce ecosystem have been talking about a setting in Setup called Opt Out of Customer Data Access. The main concern is that Allow Salesforce Access to Customer Data toggle appears to be enabled by default. This has caused admins, architects, and security teams to question what it means for their orgs and customer data. What Allow Salesforce Access to Customer Data Toggle Means This setting is related to whether Salesforce can use anonymized customer data for purposes such as research, product improvement, and AI model development. It does not mean that someone at Salesforce is casually opening your records or reading your customer data. However, it deserves attention, especially if your org contains sensitive, regulated, or confidential information. The key point is not to panic, but to understand what the setting allows, review it with the right stakeholders, and make an intentional decision instead of relying on the default. Is It New? Not Really This setting may feel new because people are now seeing the Allow Salesforce Access to Customer Data toggle in Setup. However, the concept itself is not new. Salesforce has had an opt-out process for using customer data in global models for years. The difference is that previously, opting out was typically handled through a Salesforce support case. Now, the setting is more visible and easier to manage directly from Setup. That visibility is probably why it suddenly became a hot topic. The concern is valid, but it is less about a brand-new policy and more about a long-existing topic becoming easier to notice, review, and control. Wrapping Up This setting is relevant for Salesforce orgs that use Einstein features. It may not be a brand new topic, but now that the toggle is visible in Setup, it is much easier for admins and architects to review it. The main takeaway is simple: don’t ignore the default. Check the setting, understand what it means for your org, and review it with your legal, security, and business stakeholders. Whether you leave it enabled or turn it off, it should be an intentional decision. The post Allow Salesforce Access to Customer Data appeared first on Salesforce Time.

About Pivotal Health Pivotal Health is the leading technology platform that helps healthcare providers get paid fairly in an increasingly complex reimbursement landscape. Today, many providers face persistent underpayment from health insurance companies, despite delivering high-quality care. While processes like IDR (Independent Dispute Resolution) were designed to promote fairness, they’re often administrative-heavy, time-consuming, and difficult to navigate without the right tools. Pivotal Health combines software, data, and service into a seamlessly integrated, AI-driven platform that simplifies these complex reimbursement workflows. We help providers efficiently dispute underpaid claims, reduce administrative burden, and recover the reimbursement they’re entitled to; without adding more work to already stretched teams. Our full-service IDR solution is just the starting point. We’re building solutions that enable providers to operate with clarity, control, and confidence across the reimbursement journey. About the Role We’re hiring a Data Engineer to sit at the intersection of our analytics and engineering teams. You’ll be responsible for making Pivotal’s product data accessible, reliable, and ready for analysis, connecting data sources to our warehouse, building clean transformation pipelines, and ensuring our analysts have what they need to drive business decisions. This is not a traditional software engineering role and it’s not a pure analyst role either. You’ll bring a strong technical foundation and apply it in service of business outcomes: faster reporting, better data access, and more reliable pipelines that the team can actually trust. If you enjoy building the infrastructure that makes great analysis possible and care about the business impact of your work, this role is for you. What You’ll Do Own the pipeline from product database to analytics warehouse: Take full ownership of extracting data from our PostgreSQL product database and loading it into BigQuery. Design and maintain the ETL processes that make this happen reliably, with the right structure for downstream analytics use. Bring in new data sources: Expand our analytics footprint by integrating new data sources, including third-party tools like Salesforce, into our warehouse. You’ll partner with our DevOps team to establish the right service accounts, permissions, and connection patterns to do this securely and correctly. Build and maintain analytics-ready tables: Use dbt to design, build, and manage the transformation layer that turns raw data into clean, well-structured tables. You’ll have real ownership over what the data looks like: what gets modeled, how it’s shaped, and what makes it most useful for reporting. Support reporting and business insights: Work alongside our analysts to support the reporting layer, ensuring data is fresh, accurate, and structured in a way that makes building dashboards and reports in Tableau, Power BI, or Metabase reliable and efficient. Be the bridge between analytics and engineering: Attend engineering team meetings to stay ahead of product changes that could affect analytics. Serve as the connective tissue between both teams, translating data needs into technical solutions and keeping everyone aligned. Who You Are Strong SQL skills with hands-on experience in modern cloud data warehouses: BigQuery, Snowflake, or Redshift Proficient with dbt for managing SQL transformations. You understand how to write clean, maintainable, well-documented models Comfortable with Python at a working level, enough to build and automate data workflows without needing to be a full software engineer Experience with at least one BI or reporting tool (Tableau, Power BI, Metabase, or similar) You think in business outcomes: your resume reflects the impact your work had, not just the tools you used Self-directed and comfortable with ambiguity: you can identify what needs to be done and execute without heavy guidance Collaborative by nature: you know how to work across teams with different levels of technical depth Startup or high-growth company experience: you’re used to environments where ownership is real and speed matters Extra Credit If You Have Hands-on experience with BigQuery specifically Experience connecting BI tools to a cloud warehouse (e.g., Power BI to BigQuery) Experience with Salesforce data or CRM integrations Background in FinTech, HealthTech, or other data-rich industries Why You’ll Love Working Here We’re a collaborative, low-ego team on a mission to make healthcare reimbursement fairer for providers. While we primarily hire around our core hubs–Los Angeles and New York–we remain open to exceptional talent outside those regions. Remote and hybrid flexibility varies by role and team, and is outlined in each job description. If you’re excited by solving complex problems and making a real-world impact, we’d love to hear from you. Benefits Include: Competitive compensation, including equity Full health, dental, and vision coverage Retirement savings plan through 401(k) Flexible time off Opportunities for company-wide connection and events Ready to Make an Impact?We’re building something meaningful; and we want you on the team. Bring your ideas, curiosity, and drive, and let’s transform healthcare reimbursement together. Employment Information Work Authorization Candidates must be authorized to work in the United States without current or future employer sponsorship. Equal Employment Opportunity Pivotal Health is an Equal Opportunity Employer. We celebrate diversity and are committed to creating an inclusive environment for all employees. We do not discriminate on the basis of race, color, religion, sex, gender identity or expression, sexual orientation, national origin, age, disability, veteran status, or any other legally protected status. Reasonable Accommodations Pivotal Health provides reasonable accommodations for qualified individuals with disabilities in accordance with applicable laws. If you need assistance during the application or interview process, please let us know. Background Checks Employment is contingent upon successful completion of applicable background checks, where permitted by law. At-Will Employment Employment with Pivotal Health is at-will and may be terminated by either party at any time, with or without cause or notice, in accordance with applicable law.

As a Mid-Market Account Executive, you will be working on reinforcing our leadership in the mid-market space. You should demonstrate skills associated with working in a high-performance sales culture, especially demonstrating pipeline management, lead generation, contact network development and delivering results against a quota.The Mid-Market Account Executive team’s charter is to provide the best sales experience possible to Sumo Logic’s mid-market segment customers. This Inside Sales team has a consultative sales approach, a track record of growing sales, demolishing quotas, and keeping customers happy and wanting to dive more into our product.Responsibilities• Target, manage and sell to a defined geographic territory with under 1,500 employees• Own the full sales cycle, from prospecting to close, in order to fill Sumo Logic’s pipeline• Create and deliver accurate sales forecasts• Perform product demos using web tools to prospect and customers• Partner with internal resources to provide a stellar experience for prospective customers and ensure their needs are being metQualifications and Skills• 3+ years of quota-carrying experience selling B2B applications; on-demand/SaaS, IT Infrastructure Management or Cloud Security offerings• History of quota over-achievement selling to a technical audience like IT operations, Security, and DevOps teams• Strong interpersonal and communication skills, collaborative mindset a must• Contact network within the Big Data ecosystem, highly preferred• Salesforce power userAbout UsSumo Logic, Inc. (NASDAQ: SUMO) empowers the people who power modern, digital business. Through its SaaS analytics platform, Sumo Logic enables customers to deliver reliable and secure cloud-native applications. The Sumo Logic Continuous Intelligence Platform™ helps practitioners and developers ensure application reliability, secure and protect against modern security threats, and gain insights into their cloud infrastructures. Customers around the world rely on Sumo Logic to get powerful real-time analytics and insights across observability and security sol

If you have been following the Salesforce ecosystem for a while, you probably knew this day was coming. With the Summer ’26 release, Salesforce is turning Chatter off by default in all new orgs. If you create a new Salesforce org after Summer ’26, Chatter will not be enabled by default. You will need to turn it on manually. This small change is arguably one of the clearest signs yet that Chatter is going to be retired. What Exactly Changed? Starting with the Summer ’26 release, Chatter will be disabled by default in all new Salesforce orgs. This change does not affect existing orgs created before Summer ’26. If you already use Chatter, nothing changes for you today. When Chatter is off, you lose access to: The Chatter tab and feed The Follow button Salesforce Chatter in the App Launcher Chatter groups and the Groups tab Chatter APIs If you want to enable Chatter, you can still do it from Chatter Settings in Setup. Why is Salesforce Doing This? Salesforce’s explanation is straightforward: Salesforce Channels is now enabled by default in new Enterprise and Unlimited Edition orgs. Salesforce Channels brings Slack-powered collaboration directly to record pages. For Essentials, Professional, Performance, and Developer Edition orgs, you can enable Salesforce Channels manually wherever Slack is available. The message is clear: Slack is the future of collaboration in Salesforce. Chatter belongs to the past. I Built Chatter. I’m Going to Kill Chatter If this release update did not convince you, it is worth revisiting something Parker Harris said at Dreamforce 2024. Salesforce co-founder and Slack CTO Parker Harris did not mince words: “I built Chatter. I’m going to kill Chatter”. Coming from the man who created the product, that’s not a rumor or a leak. That’s a declaration of intent. Harris also made clear that the shift to Slack, combined with Salesforce’s deep investment in AI, sets the new direction for collaboration inside the ecosystem. Chatter served its purpose for over a decade, but Slack now fulfills that purpose more effectively. The Case for Chatter’s Eventual Retirement Let’s connect the dots. In the span of a few years, Salesforce has: Acquired Slack in 2021 for $27.7 billion Launched Salesforce Channels (Slack-native integration built to replace the Chatter use case on record pages) Let its own co-founder publicly declare his intent to retire Chatter And now, with Summer ’26, stopped enabling Chatter by default in new orgs Although these are all clear signs that Chatter is being retired, Salesforce has not announced a retirement date. As of today, existing orgs continue to run it without interruption, and new orgs can still enable it manually. After his Dreamforce comments, Parker Harris also reassured users that no timeline had been set. But “no timeline” does not mean “never”. It simply means Salesforce has not told us yet. What Should You Do Right Now? If you are in a new org: Don’t build on Chatter. Design your collaboration workflows around Slack and Salesforce Channels from day one. Future-proof yourself. If you are in an existing org that relies heavily on Chatter: Start auditing your dependencies. Where does Chatter live inside your automations, Flow triggers, API integrations, or Case Feed? Map it out now, and you will save yourself serious pain when the migration comes. If you are a Salesforce partner or developer: Salesforce wants partners to build Slack-native templates and workflows. That’s where the ecosystem investment is flowing. Final Thoughts Salesforce turning Chatter off by default in Summer ’26. It is not a surprise, it is a milestone. It marks the moment Salesforce stopped treating Chatter as the default collaboration tool and started treating it as legacy. Will Salesforce retire it? Almost certainly. The co-founder said so himself. The only real question is when, and whether Salesforce will give customers a clear migration path. The post Is Chatter Being Retired? appeared first on Salesforce Time.

If you’re a sales manager trying to answer a simple question—“How many customer meetings did my team have this month?”—you might be getting the wrong answer without even realizing it. Why? Because Salesforce can quietly double (or triple) count meetings when internal attendees are involved. When your reps send meeting invites to customers from Outlook, as an example, and include other internal employees Salesforce creates a unique Event record assigned to each internal User. This creates an issue when you’re trying to figure out how many unique meeting your team has booked in a time period. Let’s take a look at an example and a workaround. I sent a meeting invite from Outlook to Test Contact (customer) and Test User (User). The Subject was “ReportForce Test”. When I run a Tasks and Events Report I can see that there are two rows with this Subject line (filtering on Subject). I’ve added a column for Activity ID (custom formula field) just to show that these are in fact two different Event records for the same meeting. As stated above, if I was trying to count how many meeting that my team had today using this Report the total would be 2, instead of the expected 1. Here’s where the solution comes in. In your Report add the Event Invitation Field. You can now see that only one record has this box checked. Since I was the sender of the meeting invite my Event record will have this Field unchecked. My colleague, Test User, was an invitee so his will be checked. Now all I need to do is filter my Report to Event Invitation = False and I will have an accurate count of meetings. Let’s see a demo of how we did this.