Part three in the delegated access series.
The approval flow: FGA resolves the approver, Auth0 CIBA sends a Guardian push, approval creates a delegation. Also: why CIBA consent does not persist across sessions, and why that's fine.
https://tobytes.com/articles/delegated-access-approval-auth0-ciba

Delegated access part three: approval flows and Auth0 CIBA
The previous post covered how a patient proactively grants a carer access to their record. This post covers the inverse: a user requests access they do not yet have, and the account holder approves it in real time using Auth0's Client-Initiated Backchannel Authentication.