Who actually does the work at Morningscale?

Stanislau Shaban, nine years of Salesforce, QA background, scopes and builds every engagement personally, with a dedicated QA lead who tests every build before it ships. No juniors, no hand-offs, no outsourcing.

How do engagements with Morningscale start?

Every engagement starts with a free 30-minute call. We look at the manual work and where things break, then investigate the real workflows and send a written scope with a fixed price before any work begins.

Does Morningscale offer on-call or emergency Salesforce support?

No, support is deliberately async: a defined monthly scope with a 48-hour response and no emergencies. Every build ships with error logging, monitoring, and documentation so silent failures are caught by instrumentation rather than fought as emergencies.

How does Morningscale test automations?

Every build passes a written QA process: a pre-deployment checklist, a 200-record bulk test, a permission-matrix test, fault-path coverage (nulls, recursion, partial writes), and an error-log framework so nothing fails silently. Documentation and a UAT sign-off close every build.

How is AI (Agentforce) handled safely in Salesforce?

The same way as code: tested before it touches a real customer. Agents get scoped data access, human-in-the-loop approval, and the same QA process as any automation. BYO-LLM is supported so sensitive data never leaves the client perimeter or trains an external model.

Where is Morningscale based and do they work globally?

Morningscale is based in Poland and works worldwide, async across time zones, in English, Russian, and Polish.

← All posts

CRM & Salesforce automationAugust 20, 20261 min read

Salesforce's Retirement of OAuth Username-Password Flow: Implications for Real Estate CRM Integrations

Salesforce's deprecation of the OAuth 2.0 username-password flow in Winter '27 necessitates immediate action for real estate firms to maintain secure CRM integrations.

Salesforce has announced the deprecation of the OAuth 2.0 username-password flow for connected apps, effective with the Winter '27 release. This change requires real estate firms to transition their CRM integrations to more secure authentication methods to ensure uninterrupted operations.

Key Details

Deprecation Timeline: The OAuth 2.0 username-password flow will be retired in Winter '27. Sandbox preview instances will upgrade on August 28-29, 2026, with production instances following on October 9-10, 2026. (trailblazingwithsalesforce.com)
Recommended Alternatives: Salesforce advises transitioning to the client credentials flow or the JWT bearer flow for server-to-server integrations. User-facing applications should adopt the web server flow with PKCE. (trailblazingwithsalesforce.com)

Implications for Real Estate Firms

Real estate companies often rely on automated lead routing, data synchronization, and other integrations between their websites, CRM systems, and third-party platforms. The retirement of the username-password flow means that any integration currently using this method will cease to function post-upgrade unless updated.

Action Steps:

Audit Existing Integrations: Identify all systems and applications that utilize the OAuth 2.0 username-password flow for authentication.
Plan Migration: Develop a strategy to transition each integration to one of the recommended authentication methods.
Test Thoroughly: Before the production upgrade in October, test all updated integrations in a sandbox environment to ensure they function correctly.

By proactively addressing this change, real estate firms can maintain the reliability and security of their CRM integrations, ensuring seamless operations and data integrity.

For assistance in updating your Salesforce integrations, consider scheduling a consultation with our team to ensure a smooth transition.

Want this reliability in your org?

Book a short, paid Automation Health Audit. We'll read your org and hand you a ranked map of what's running, what's risky, and what's worth fixing.

Book your audit call →