Today4 stories · 1 brief

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 27The independent daily for Salesforce admins, developers and architects4 stories · 1 brief

Must-readArchitecture

Scaling Experience Cloud Person Accounts past the 50,000 ownership limit (opens in a new tab)

You will learn how the 50,000 account-ownership limit and the external role allocation differ for role-based Experience Cloud licenses, and what options exist for a 200,000-customer Person Account portal.

Why read this

The reader will also see why license choice should be settled before deployment.

Single internal owner

  • All 200,000 accounts under one user
  • Hits the 50,000 ownership limit
  • Support increase request not approved

Person Account Owner Power User

  • One eligible power user owns more accounts
  • Power user must sit at top of role hierarchy
  • Set up with deferred sharing disabled
Two ways to handle the 50,000 account-ownership limit for Person Accounts

The author describes a production problem on an e-commerce Experience Cloud portal meant to onboard about 200,000 customers. The portal used Person Accounts and the Customer Community Plus Login license, which requires an external user role. When user creation hit a 50,000 account-ownership constraint, Salesforce Support declined the requested increase, leaving the site live in production but unable to proceed with the planned onboarding. The piece stresses that this 50,000 ownership limit, the org-wide external role allocation (documented default of 50,000 for role-based external licenses) and total external user capacity are separate constraints, and that creating 200,000 users does not necessarily consume 200,000 roles.

The article sets out four options. The first is the PersonAccountOwnerPowerUser setup object, which lets an eligible internal user at the top of the role hierarchy own more than 50,000 qualifying portal accounts; it carries restrictions on the role and on deferred sharing, and does not change role allocation or other license limits. The second is spreading ownership across several internal users, which reduces per-owner load but adds sharing, reporting and maintenance complexity. The third is checking whether Customer Community, a high-volume non-role-based license, would meet the business needs, after assessing sharing, reporting, Apex and cost differences. The fourth is requesting a limit increase from Salesforce Support, which is not guaranteed and should not be the only plan.

The author then lists common mistakes, such as treating 50K as the total user limit, ignoring Person Account ownership in early design, choosing a license only because it supports roles, relying on support exceptions, and neglecting data isolation when owners or roles change. A pre-production checklist covers volume forecasting, license confirmation, limit validation, ownership and sharing strategy, customer data isolation, restartable bulk provisioning, early validation with Salesforce, and a fallback plan. The core lesson is that licensing, ownership, role allocation, sharing and provisioning must be settled in the initial design rather than discovered during production rollout.

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

Worth reading?

RecommendedDevOps

What a local Apex runtime sends off the machine, and what it keeps (opens in a new tab)

You will know where Apex source, test data and licence details go when renmy runtime runs, which settings turn telemetry off, and how it works offline and air-gapped.

Why read this

It is the questionnaire answers a security or procurement team will ask for.

Org-based test runs

  • Each test run deploys to a Salesforce org
  • Test data sits in the org sandbox
  • Each developer needs an org credential

Local runtime

  • Tests run on the developer's machine
  • Test data lives in an in-process database
  • Test runs need no org or credential
Where Apex runs and where data lives, before and after a local runtime

This vendor-written piece, published by Renmy UG of Berlin, gives security and procurement teams the answers they need for a questionnaire about renmy runtime, a local Apex runtime formerly called Nimbus. It executes Apex, SOQL, DML and Salesforce Flows on a developer’s machine against an embedded PostgreSQL, without an org, Docker or a JVM. Apex source is read locally and sent to no one. Tests run against schema read from the project’s metadata, so they need no connected org, and test data sits in an in-process database with no open network port, rolled back after each test.

The article then sets out what leaves the machine. The Free tier needs no network access. By default the runtime sends one privacy-minimal activation event to an EU-hosted service, which excludes code, paths, test names and record data. Pro licences also record one de-duplicated activation from headless CI. Either can be switched off with a single setting or environment variable. Pro and Team licence checks send the licence key to the Keygen licensing API, at most once a day. Activating a machine with renmy login also sends a hashed installation ID, hostname, display name, OS, architecture, CPU core count and account ID. Licences are cached for offline use for up to seven days.

For disconnected networks, the article says the binary can be copied into place without internet access, since the database engine is embedded, and the daily update check can be disabled. Enterprise customers can have licence validation on premises, with pricing from $20,000 a year. A command-by-command table lists what each command contacts. The Salesforce org remains the system of record and deployment target. The deploy flow validates the same payload in the org before deploying, and Pro release commands produce signed receipts for auditors.

The piece closes with a list of documents to attach to the questionnaire, including the security page, data processing addendum, subprocessor list and licence terms. It also gives pricing: Free at $0, Pro and Team free during the public beta with listed prices of $19 and $49 per month, and Enterprise on a custom contract.

Read the original at dev.to (opens in a new tab)

Worth reading?

Flow and admin

Prototyping Screen Flows and record pages before building in a sandbox (opens in a new tab)

You will learn a four-step pre-build method for mapping and mocking up Lightning pages and Screen Flows with stakeholders, and when to choose Dynamic Forms over a Screen Flow.

Why read this

You will also see how to turn the approved prototype into a field dictionary and Gherkin acceptance criteria.

  1. Map the process swimlane
  2. Prototype the record page in SLDS
  3. Test visibility and edge cases live
  4. Export data dictionary and Gherkin
The four steps from discovery to a spec ready for sandbox configuration

The author opens with a familiar failure: a discovery workshop produces a requirement that is then built in a Developer Sandbox over two days, only to be reworked after a playback call. He argues that the gap is stakeholders not being able to picture how a written user story becomes a real Lightning page or Screen Flow until they see it, and that generic tools fall short. Written stories, Figma or Miro canvases, and prototyping in a sandbox each fail for Salesforce in different ways, so the prototype should stay within SLDS constraints.

The method starts with mapping the process swimlane using Universal Process Notation, identifying the trigger, decision gateways, and whether the user needs a guided wizard or persistent fields with conditional visibility. A rule of thumb is given: use Dynamic Forms with Path guidance for ongoing single-record updates with a few conditional fields, and a Guided Screen Flow for multi-step wizards, related child record creation or verification before advancing a stage. The prototype is then reviewed across four zones of the Lightning page: the Highlights Panel, Path stages with guidance text, two-column detail sections, and sidebar Related Lists.

The author then recommends testing conditional visibility and edge cases live, including negative paths, persona-based editability, and console density. Finally, the approved prototype is converted into a field-level data dictionary and Given/When/Then acceptance criteria before any sandbox configuration begins. The approach is presented as a 15-minute pre-sandbox routine, though the article is aimed mainly at admins and business analysts.

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

Worth reading?

Agentforce and AI

Salesforce unveils AIforce apps linking platform data to Claude and Slack (opens in a new tab)

You will learn what the three AIforce applications are, what each does with Salesforce data, and what the Claude Code plug-in adds for developers.

Why read this

The piece is a brief overview without implementation detail.

AIforce initial release

  • Claudeforce
  • Slackforce
  • Agentforce Coworker
The initial AIforce release is made up of three applications

Salesforce announced AIforce at Dreamforce, a set of applications that connect platform data and workflows to Claude and Slack. The initial release has three parts: Claudeforce, Slackforce and Agentforce Coworker. Claudeforce comes out of an expanded partnership with Anthropic and ships with 37 pre-installed sales capabilities, from prospecting to opportunity management, plus a Claude Code development add-on with more than 40 further tools. Deloitte, GitLab and Legora piloted it, and it is now in beta for all customers.

Slackforce brings Salesforce data into Slack conversations, letting teams combine information from different sources, apply filters and take actions through interactive surfaces. The upgraded Slackbot assistant and Slack CRM feature can update files and create records from simple text commands.

Agentforce Coworker works inside Salesforce’s internal Lightning environment as a digital assistant that uses customer history and activity. According to the company, it needs no data migration or new permission settings, and it recorded 100,000 activations in its first 35 days.

Read the original at dev.to (opens in a new tab)

Worth reading?

In brief