Answered Sam's question about the RingCentral panel banner shown in Litify/Salesforce. Loaded the Litify live defaults skill, searched memory for the prior RingCentral lane, checked RingCentral's current Embeddable documentation, and performed a read-only live Salesforce Tooling API readback against LITIFY_ORG.
RingCentral's Embeddable documentation says the FOR DEMO PURPOSES ONLY banner appears when the default bundled client ID and secret are used, and that registering a dedicated app and passing its clientId removes the banner.
Live Tooling API readback confirmed the active LWC is litifyRingCentralPanelV2, and its RingCentral iframe URL is https://apps.ringcentral.com/integration/ringcentral-embeddable/latest/app.html?prefix=sail-litify-ringcentral-20260519&enableSMSTemplate=1&enableSmsSettingEvent=1. It does not include a custom clientId.
Memory from the May 19 RingCentral repair shows this was expected: the custom RingCentral client ID was removed because it was tied to a broken Developer Console app that produced OAU-113, no redirect URI registered. That removal unblocked staff sign-in, with the tradeoff that staff may see the demo/default-client banner until a dedicated RingCentral Embeddable OAuth app is configured.
Done for explanation. No Salesforce, RingCentral, or repo changes were made in this session.
The question was answered and live-validated read-only.
The clean production fix is to create or repair a dedicated RingCentral Embeddable OAuth app, configure the correct redirect URI, and update the Salesforce LWC iframe URL with that app's clientId after check-only deployment and rollback capture. This should be done carefully because the prior custom client ID caused staff sign-in failure.
Use the existing RingCentral/Litify lane. Do not re-add the old broken client ID. Start with the live LWC litifyRingCentralPanelV2, the active flexipage Collapsible_Matter_Page, and the May 19 rollback context. Keep the fix narrow: dedicated Embeddable OAuth app, verified redirect URI, check-only deploy, live deploy, Tooling readback, browser QA on a live Matter record. Preserve the temporary working no-clientId state as the rollback path.