What a request shows
Each request shows the requester, the resource, whether it is a read or a save, the reason in the requester's own words, and the time left to answer. More information shows the source host, the network address the server saw and what your approval signs, each marked Verified, Observed or Reported by requester.
You choose the length
Approve for the requested time or change it: by default 5m, 15m, 1h, 6h, 24h, 7d or Always, or a custom length up to the resource's limit. Choosing longer than requested asks you to confirm. Your server sets the choices.
Deny, or flag it
Deny a request you know about. I don't recognise this denies it, flags it in the approval log, and shows the commands your administrator can use to revoke that requester's key or end every grant at once.
Grants and history
Grants lists the access you approved, with Revoke to end it early. History lists every decision, newest first.
Notifications without secrets
Where push is set up, a notification carries only random IDs and the app fetches the details from your own server. On Android you can opt in to approving from the notification. Phone notifications from your own server to the official apps aren't available yet: they need a sending key for S6 Studios' notification project, which we don't hand out. Until that changes, the apps show waiting requests whenever you open them.
Approval key design
The official apps use Android Keystore, iPhone Secure Enclave or a Windows Hello passkey. Android can use a per-signature biometric key. The server can't verify these equally on every platform; see the security model.