- Ya
- 4 Septemba 2026, 02:48 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 2958435
Each OAuth2 card on Platform Configuration → Advanced gets an enable/disable switch in its top-right corner. It writes only the enabled flag, is unavailable until credentials exist behind it, and reverts if the write fails — an enable/disable that shows the state the operator asked for rather than the one the server kept would be worse than no switch. Its tooltip says what switching off actually does, since the effect lands on other people's screens. The org side is the other half. OrgOAuthAppSection is one component, dropped into every settings screen that connects through one of these providers: email mailboxes, meetings, Teams phone, social, Canva and payroll. It asks one question — Kamo's application, or one you registered yourself — and renders the credential form for the second. When the platform registration is switched off the question disappears rather than becoming a disabled radio: there is nothing to choose between, and the credential form is the only way forward. That case is the point of the feature, so it gets the plain path, not the greyed-out one. The provider field schema moves to a shared catalog both sides import. They describe the same registration; a field added for the platform and not for the org would be a credential an org could never supply, and it would surface only as a provider rejecting the token request. The registrations load through one shared, invalidate-on-write cache — the email screen alone renders three sections, and each fetching for itself would issue the same call three times per visit.