- Shipped
- September 5, 2026 at 6:34 AM UTC
- Author
- Kamo
- Commit
- 18fd4e5
Offboarding deleted the member's credential row when they were moved off a phone server. That was the whole job while the credential could only be a JWT — Kamo cannot revoke one of those anyway, it is done in RingCentral's own console. A refresh token is different: one Kamo merely forgets stays live at RingCentral for its full lifetime, and nobody but the member would ever see it. Routes offboarding through the same disconnect path the card's button uses, which revokes before deleting. Guarded on the old instance still existing and still being RingCentral, and the plain delete stays behind it so a row is dropped even when there is nothing left to revoke against.