- Shipped
- July 8, 2026 at 10:32 PM UTC
- Author
- Kamo
- Commit
- 315f8a4
The per-member RingCentral flow was self-serve only, so an admin managing another member's profile saw "they must connect it themselves". Sysadmins commonly create the member's RingCentral account and hold their credentials, so they should be able to connect on the member's behalf. - OAuthController member start/status/disconnect now accept an optional target memberId. Acting on another member requires MANAGE_EXTENSIONS or MANAGE_VOIP_SETTINGS (mirrors the profile-edit gate); self is always allowed. - start also verifies the target member is actually assigned that instance (the instance is org-scoped, so this confirms same-org). - Whoever completes the RingCentral login still determines the identity; the assigned-vs-connected extension guard flags a mismatch.