Summary

Continued the RingCentral-first Litify communications build after the Matter/Intake panel production deployment. The priority stayed within the approved scope: RingCentral is the live call/message action surface, Salesforce/Litify is the context and record trail, SMS Magic history is preserved, and no RingCentral outbound API write path was added.

What was accomplished

• Verified the deployed controller class exists in production as LitifyRingCentralContextController.
• Checked active staff profile counts for normal-user exposure.
• Retrieved staff profiles and confirmed the new controller was not present in normal profile metadata.
• Confirmed the existing Litify_Apex_Class_Access permission set was assigned only to admin/service-style users and would not prove staff visibility.
• Created and deployed a narrow permission set: RingCentral_Panel_User.
• Permission set scope: Apex access to LitifyRingCentralContextController only.
• Check-only deploy succeeded: 0AfUV000001WdSH0A0, 1 component validated, LitifyRingCentralContextControllerTest 3/3 passing.
• Production deploy succeeded: 0AfUV000001WdTt0AK, 1 component deployed, LitifyRingCentralContextControllerTest 3/3 passing.
• Assigned RingCentral_Panel_User to 45 active human users across Litify Accounting User, Attorney, Intakes Agent, Intakes Manager, Legal Assistant, Marketing User, Paralegal/Case Manager, Partner (SAIL), Power User, and Standard User profiles.
• Excluded System Administrator, API-only, integration, and null-profile users from the assignment target.
• Re-queried live assignment counts by profile and confirmed 45 assignments remain active.
• Retrieved the deployed permission set into tmp/ringcentral-normal-user-access-2026-05-13-postdeploy/.
• Added rollback script at tmp/ringcentral-normal-user-access-2026-05-13/rollback_ringcentral_panel_user_assignments.apex.
• Updated RingCentral handoffs and the QA queue with the access patch, deploy IDs, remaining proof gates, and rollback location.

Reason for ending

This checkpoint ends after backend normal-user access was patched and verified. The next gate requires rendered Lightning/browser behavior, RingCentral iframe/session behavior, microphone/call/text behavior, mobile sync, and notification proof. Those are more interactive than the backend metadata/deploy work completed here.

Current state