Today4 stories · 2 briefs

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 19The independent daily for Salesforce admins, developers and architects4 stories · 2 briefs

Must-readDevOps

Salesforce makes email the default Login on its standard Login pages (opens in a new tab)

You will learn which login pages change and when, what stays the same for passkeys and MFA, and what admins should do about users, shared inboxes and automated UI tests before the rollout reaches production.

  1. Enter the email address
  2. Receive a verification code by email
  3. Choose the org in the environment switcher
  4. Or click Login with Username
Login order on login.Salesforce.com once email becomes the default

Salesforce has announced that the login pages at login.Salesforce.com and test.Salesforce.com will ask for an email address first, with username login still available through a Login with Username link. The change was first described in the Spring ’26 release notes and was communicated to admins by email in September. Sandboxes are scheduled for August 2026 and production for October 2026, while mobile apps are tentatively planned for late 2026. My Domain and Experience Cloud login pages are not affected.

The article notes that a username-first experience is also being rolled out on My Domain login pages, and that Salesforce describes passkeys as the fastest, easiest and most secure way to sign in. Salesforce’s stated reason for email login is a unified login process in which a user types one email and sees every org they can access. The author could not find a clear security rationale for the change. Email login sends a verification code, and the environment switcher lists the matching orgs. Problems arise when a user’s email and username differ, or when one email maps to several usernames.

The community is split. Supporters find the flow smooth and note that passkeys reduce clicks. Consultants and partners with many orgs find the extra selection step costly. An IdeaExchange request asking Salesforce not to make email the default has gathered 760 points, arguing that an email lookup can reveal every environment tied to it. Salesforce said at True to the Core that email login still requires access to the inbox, and that it is working on auto-favoriting login hints for multi-org users. The article’s advice is to check for shared inboxes, tell users to use the My Domain URL, and add ?login=1 to automated test URLs so they reach the username screen.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

RecommendedData Cloud

Cutting Data 360 credit costs through ingestion choices (opens in a new tab)

You will learn how Data 360 credits are consumed by rows processed, and how the choice between zero-copy, batch and streaming, and query or file federation changes that cost.

Why read this

You will also see when internal CRM pipelines are free.

Zero-copy

  • About 70 credits per 1 million rows
  • Best for infrequent or ad-hoc queries
  • Data must stay in external lake

Standard ingestion

  • 500 to 2,000 credits per 1 million rows
  • Cheaper for frequent queries and transforms
  • Copies are acceptable
Zero-copy and standard ingestion differ in cost per million rows and in when each is cheaper

Data 360 credit consumption for many usage types is driven by the number of records processed or accessed, not by the rows returned. The article argues that pipelines which scan large volumes but return few rows waste credits, so architects should decide how data enters the platform before anything else. Data kept outside the platform, or filtered before ingestion, incurs no processing cost, and zero-copy avoids replicating data at all.

The article compares zero-copy with standard ingestion. Zero-copy suits infrequent or ad-hoc queries and data that must stay in an external lake, at roughly 70 credits per million rows processed plus compute on both sides. Standard ingestion, at 500 to 2,000 credits per million rows, is more economical when data is queried frequently and transformed. Streaming costs more than batch because of continuous micro-batching and index updates, so batch should be used unless near-real-time freshness is needed. Core CRM pipelines from Sales Cloud, Service Cloud, Marketing Cloud and B2C Commerce have consumed zero credits since August 2025, though some Industry Cloud connectors still incur standard usage.

For zero-copy, the article contrasts query federation over JDBC, which bills compute on both Data 360 and the external source and is best for datasets under 100 million rows, with file federation over Apache Iceberg, which reads storage directly, is faster on datasets over one billion rows, and has native change capture and Flow automation. It recommends enabling acceleration for frequently queried zero-copy data to avoid repeated external compute charges.

Read the original at Salesforce Architects (opens in a new tab)

Worth reading?

Flow and admin

How to enable and assign the Slackbot UI permission in Salesforce (opens in a new tab)

You will learn how to connect your Salesforce org to Slack and configure the Slackbot UI system permission so users can access the agent directly in Lightning Experience.

  1. Connect Salesforce org to Slack workspace
  2. Create a Permission Set for Slackbot
  3. Enable the Slackbot UI system permission
  4. Assign the Permission Set to users
The setup sequence for giving users access to Slackbot in Salesforce Lightning

The article outlines the configuration steps required to make Slackbot available inside Salesforce Lightning Experience. Before any user-facing features can be enabled, administrators must link their Salesforce org to a Slack workspace through the Manage Slack Connection setting and accept the pending request.

Access is controlled via a dedicated system permission called Slackbot UI. Administrators create a Custom Permission Set, navigate to System Permissions, check the box for the Slackbot UI capability, and save the changes. The Permission Set is then assigned to individual users or groups who require access.

Best practices emphasize validating the connection in a Sandbox first, using a dedicated Permission Set for easier auditing, and setting assignment expiration dates for pilot phases. The guide also notes that using Slackbot may require Flex Credits approval from a Salesforce administrator, and recommends verifying that the agent respects existing object and field-level security before full deployment.

Read the original at InfallibleTechie (opens in a new tab)

Worth reading?

Flow and admin

Manually enter a default no-reply address in Salesforce Flow without changing its configuration (opens in a new tab)

You will learn how to send emails through Salesforce Flow using an Organization-Wide Email Address configured exclusively as a default no-reply sender.

Why read this

The guide explains the manual entry workaround and advises validating the behavior in your own org before deploying to production.

  1. Add an Action element and select Send Email
  2. Set Sender Type to OrgWideEmailAddress
  3. Type the address into Sender Email Address
  4. Or pass a Text resource holding the address
How to send a Flow email from a Default No-Reply Address without changing its purpose

Salesforce Flow hides Organization-Wide Email Addresses that are configured strictly as default no-reply senders. While changing the address purpose to allow user selection works, it modifies existing configurations that may rely on the restricted setting.

The recommended approach bypasses the dropdown menu entirely by typing the exact email address directly into the Sender Email Address field. A Text resource holding the address can also be passed to the same field. Salesforce documentation supports using Text resources to supply Organization-Wide Email Addresses, which makes this method functionally sound.

The author notes that this behavior acts as a tested workaround rather than an officially documented exception for default no-reply addresses. Readers should verify the flow in a test environment to ensure consistent email delivery before implementing it in live business processes.

Read the original at Salesforce Time (opens in a new tab)

Worth reading?

In brief