Today4 stories · 1 brief

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

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

Must-readFlow and admin

Automate temporary access management with Permission Set expiration dates (opens in a new tab)

You will learn how to configure automatic expiration dates on Permission Set assignments and manage them individually or in bulk.

Why read this

The piece outlines best practices for temporary access scenarios and highlights important considerations for compliance and user communication.

Old Method

  • Manually remove permissions later
  • Trust memory or calendar reminders
  • Use deprecated session-based activation

New Automation

  • Set expiration on Permission Set assignments
  • Choose fixed dates or relative day counts
  • Automatically lapse access for clean audits
Contrasting manual permission revocation with automatic expiration dates

Salesforce now allows administrators to set expiration dates directly on Permission Set assignments, eliminating the need for manual revocation of temporary access.

Administrators can configure expirations when adding individual assignments or use the Manage Assignment Expiration action in Setup for bulk updates. The system supports both fixed calendar dates and relative day counts for recurring temporary needs.

The feature benefits contractors, project teams, and compliance audits by ensuring access lapses automatically. The author warns that expiration happens silently, recommends automating recurring assignments with Flow, and notes that this model replaces the deprecated session-based activation approach.

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

Worth reading?

RecommendedArchitecture

Evaluating customer portal architectures by measuring ongoing admin and release overhead (opens in a new tab)

Readers will learn how to evaluate platform versus off-platform portal architectures by comparing their impact on Sharing Rules, API limits, and release testing.

Why read this

The piece provides concrete questions to ask before kickoff so teams understand who owns security and maintenance after launch.

The article outlines three approaches to building customer portals: native Experience Cloud sites, custom off-platform applications using APIs, and third-party pre-built solutions. It argues that the choice should be driven by long-term administrative overhead rather than initial development speed.

Visibility and security behave differently across each path. Platform builds rely on Salesforce Sharing Sets, external roles, and guest user access rules, which can be bypassed by insecure Apex code. Off-platform and pre-built options delegate record filtering to application code or vendor settings, requiring careful control over the integration user permissions.

Ongoing costs diverge significantly after deployment. Native portals consume transaction limits and demand rigorous test coverage during quarterly releases, while external integrations draw heavily from the daily API request pool and must track API version retirements and authentication changes. The author recommends assigning dedicated integration users, requesting written call budgets, and verifying vendor certification timelines before go-live.

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

Worth reading?

Agentforce and AI

Salesforce announces Agentic Identity and flex credit adjustments for Model Context Protocol servers (opens in a new tab)

Readers will understand how Model Context Protocol servers connect Salesforce to external systems through natural language prompts.

Why read this

They will also learn about the upcoming November changes to the flex credits model and the new Agentic Identity framework for agent permissions.

The article introduces Model Context Protocol servers as a standardized interface for linking artificial intelligence hosts to enterprise systems like Salesforce. It outlines a three-part architecture comprising a host application, a client, and a server that securely exposes tools and resources. This design aims to replace custom integrations by allowing large language models to automatically discover and execute connected capabilities.

Practical examples demonstrate how sales and support teams can retrieve pipeline data or automate cross-platform workflows using simple natural language commands. These scenarios eliminate the need to manually switch between separate applications and navigate multiple forms to complete routine tasks.

Financial and governance impacts are also addressed, noting that agent-driven calls will begin consuming standard flex credits in November. The piece explains the introduction of Agentic Identity to distinguish between standard user operations and scoped agent permissions. Testing environments including Sandboxes and Scratch Orgs remain exempt from these billing changes, allowing teams to evaluate the technology safely before production deployment.

Read the original at Nebula Consulting (opens in a new tab)

Worth reading?

Apex and platform

How to write effective Apex tests that pass deployment gates and avoid common pitfalls (opens in a new tab)

You will learn the exact platform requirements for Apex test coverage and how to structure tests that actually validate business logic instead of just inflating percentages.

Why read this

The piece also outlines practical patterns for bulk-safe test data and deployment troubleshooting.

The article explains that Salesforce enforces mandatory Apex test runs to protect multi-tenant reliability and prevent regression. Production deployments require at least seventy-five percent org-wide code coverage, complete trigger coverage, and zero failing methods, though test classes themselves are excluded from the calculation.

It emphasizes that coverage metrics alone do not guarantee quality, urging developers to replace empty test methods with explicit System.assert calls that verify business outcomes rather than implementation details. Writers are advised to cover both happy and unhappy paths, including validation failures and governor limit boundaries.

Practical guidance follows for building robust test suites, recommending the use of @TestSetup for shared fixtures, centralized test data factories, and inserting two hundred records to simulate bulk trigger behavior. The piece also clarifies how Test.startTest and Test.stopTest reset governor limits and synchronize asynchronous executions.

Finally, it lists common deployment hurdles such as coverage resetting after metadata edits, mixed DML errors when creating users alongside other objects, and the recommendation to target ninety percent coverage for safety margins. Individual class debugging is suggested to isolate failures quickly.

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

Worth reading?

In brief