Summary of work done

• Verified the live Litify Matter RingCentral tab in Chrome on May 22, 2026.
• Confirmed the active iframe URL is still the V2 cache-busted embeddable URL without a custom clientId, so the banner says FOR DEMO PURPOSES ONLY.
• Confirmed the old saved RingCentral clientId is unsafe for this panel because it belongs to the SMS Quick Start JWT app and fails the Embeddable redirect URI check with OAU-113.
• Used the live Salesforce session and RingCentral browser flow to sign Sam into the embedded RingCentral panel. The first-run blocker was RingCentral's emergency-calling registered-address consent. After accepting it, the embedded dialer loaded inside the Matter page.
• Verified the RingCentral tab now shows Phone, Dialpad, Calls, Voicemail, Recordings, and Text inside the live Litify Matter page for Terry Myrick.

What has shipped

• Sam's current Chrome/Salesforce session is signed into RingCentral inside the Litify panel.
• No Salesforce metadata was deployed, because deploying the old clientId would recreate the staff OAuth failure.
• No RingCentral Developer app was created, because the Developer Console account-selection page rendered blank even after the RingCentral app session was authenticated.

Why staff were confused

• Staff being logged into the local RingCentral desktop app is not enough for the Litify iframe. The iframe is a browser OAuth session and stores its own authorization state in the browser.
• Staff may see a RingCentral sign-in flow and, on first run, an emergency-calling registered-address consent screen. They need to complete that browser flow once in the Salesforce browser context.

Remaining blocker

• To remove the demo banner, create or repair a dedicated RingCentral Embeddable 3-legged OAuth app with redirect URI https://apps.ringcentral.com/integration/ringcentral-embeddable/latest/redirect.html, then deploy its clientId into the Litify panel after validating the authorize URL does not return OAU-113.
• The current Developer Console web flow is blocked at blank #/selectAccount, so a user-visible console session or alternate working developer-console path is needed before the banner can be removed safely.

Suggested next steps

• Best next move: open the RingCentral Developer Console in Chrome, get past the account-selection page, then create the SAIL Litify RingCentral Embeddable app using the prefilled new-app URL already tested in this session.
• After the app is created, validate the new clientId against the Embeddable redirect URI before touching Salesforce.
• Then update only litifyRingCentralPanelV2 or a safe Salesforce label pattern, run a dry-run deploy, deploy, and confirm the live iframe URL has clientId= and no demo banner.