Checked live Salesforce/Litify through LITIFY_ORG for Janelle Aguiar and the RingCentral iframe panel.
Live findings:
janelle@kylawoffice.com, is an active Salesforce user on the Litify Power User profile.LastLoginDate showed activity on May 19, 2026.RingCentral_Panel_User, label RingCentral Panel User.RingCentral_Panel_User.RingCentral_Panel_User permission set grants access to Apex class LitifyRingCentralContextController, which is the controller the Litify RingCentral panel uses.litifyRingCentralPanel exists, is exposed, and targets litify_pm__Matter__c and litify_pm__Intake__c record pages.Summaries, History, and SMS Templates. It shows the iframe on desktop only when Call or SMS is selected. On mobile, it opens the RingCentral mobile path instead of showing the embedded iframe.This does not look like a missing Salesforce permission for Janelle. The most likely explanation is user workflow or session state: wrong record type, default Summaries view, mobile behavior, not clicking Call or SMS, or RingCentral browser login/cookie state.
The live permission and component checks answered the immediate question. No Salesforce writes were made.
If the problem persists, a future agent can inspect the exact screen state with a screenshot or a short live browser QA pass. The first things to confirm are whether Janelle is on a Matter or Intake record, whether she selected Call or SMS, whether she is on desktop, and whether RingCentral is signed in inside the embedded frame.
Use LITIFY_ORG and the litify-live-defaults skill. Treat this as already permission-validated unless Salesforce assignments changed after May 19, 2026. Do not assign additional permissions without new evidence. The relevant permission set is RingCentral_Panel_User; the relevant component is litifyRingCentralPanel; the relevant Apex controller is LitifyRingCentralContextController. If doing UI follow-up, compare desktop behavior on a Matter or Intake record with the component states: Summaries and History hide the iframe, while Call and SMS show it. Mobile intentionally routes to RingCentral mobile instead of embedding the iframe.
Read-only live checks only. Verified user status, profile, permission set assignment, permission set grant to the Apex class, LWC exposure, supported objects, and workspace display logic. No live changes were made.