Manual for Bouncer 0.5.7. Chapters state version and distribution limits. Source cdd3b59, site build 20 November 2026. Your server or app may run an earlier version.
On this page
Answer requests
When someone asks for access to a resource you're an approver for, the request comes to every device you've paired. Answer it on any one of them.
Where requests show up
- Inbox. Open Bouncer: the Inbox tab lists everything "Waiting for you", with a count. Each card says who wants what and how long is left to answer. "Nothing waiting" means there's nothing to answer.
- Android notifications. A notification arrives even when Bouncer is closed. On the lock screen it says only "Access request pending" and "Unlock your phone to see the details". Once the phone is unlocked it shows who wants what. The notification carries only a random ID; the app fetches the details from your server. If it can't, it says "Couldn't load the details. Open Bouncer to review it."
- Windows notifications, while Bouncer is running in its window or the tray. Choose Open to see the request. The tray icon shows how many requests are waiting.
Read the request
A request opens with one line saying who wants to do what, for example "deploy-bot wants to read prod-db-password". Under it:
- The reason, labelled as the requester's own words and "not checked by Bouncer". Treat it as a claim, not a fact.
- Who is asking: a person, an automation (a script, service or AI agent), or a host. "Your own request" or "Your own automation" means it's yours.
- The requesting app, exactly as the requester reported it, or "No app reported". The icon follows that text and isn't proof of the app.
- The credential, with Read or Save · N fields. Read means the requester wants to read the value. Save · N fields means it wants to write new values into that many fields, not read them.
- What approving does, in one sentence. For a read: the requester can read the credential until access ends, anything already read can't be taken back, and open sessions may continue. For a save: one update of the named fields, and no read access.
- The time left to answer, for example "4 minutes left to answer". This is not how long access lasts; see Approvals and access duration.
Tap More information for the source host, the network address the server saw, the requester key, what your approval signs, and the request ID. Each detail is marked Verified, Observed or Reported by requester, so you can tell what Bouncer checked from what it was told.
If you weren't expecting the request, deny it.
Approve
- Check Access for. It starts at what was asked for, marked Requested. On a phone, tap Change to pick another length (How long access lasts). Windows cannot change it: Approve gives the length asked for, so answer on your phone to choose another length.
- Tap Approve. On a phone the button names the length, for example Approve 1 hour or Approve 15 min; for a save it says Approve save.
- Confirm it's you if the device asks:
- Android: the phone must be unlocked. If you chose fingerprint approvals when pairing, put your finger on the sensor.
- Windows: Windows Hello asks for your PIN, face or fingerprint.
- You should see Approved for the length you chose, with when access ends. The requester can now use the credential.
On Windows you can also use the keyboard. Esc denies. Enter approves only when nothing has keyboard focus. If a button has focus, Enter presses that button, so Enter on Deny denies. Windows Hello still asks either way.
Deny
- Tap Deny. You get Deny this request? with two choices:
- Deny: "You know about this request, but it shouldn't go ahead."
- I don't recognise this: deny it and mark it as not recognised in the approval log.
- You should see Denied. The requester sees that it was denied.
If you choose I don't recognise this, the app shows Denied and flagged
and explains that someone else may have that requester's key. It shows the
commands your administrator can run on the server: one to revoke that
requester's key, and bouncer-admin revoke --all to end every grant and
revoke every token at once. Tell your administrator.
On Windows, Deny signs straight away with Windows Hello. There is no Deny this request? step or I don't recognise this choice. If you do not recognise a request, deny it on your phone so it is flagged in the approval log, or deny on Windows and tell your administrator.
Approve or deny from an Android notification
You can add Approve and Deny buttons to request notifications:
- Open Settings.
- Under Notifications, turn on Approve from notifications.
It's off by default. The phone signs this change and saves it on your server, so you need to be online to turn it on.
Then:
- Approve from a notification approves for the requested duration only. To choose another length, tap the notification to open the request.
- The phone still has to be unlocked, and asks for your fingerprint if you chose that when pairing.
- Every request notification has Review, which opens the request. A resource can refuse approval from notifications; its notifications then offer only Review. Approve is also left out when the requested duration isn't allowed, or when it's your own request on a resource that needs another approver.
- A save request's notification says "One-time save" and offers Approve save.
iPhone alerts and Windows notifications have no approve or deny buttons.
On Windows
The Windows app approves only after you turn on Windows Hello approvals. Until then, a request shows Approve on another device, and you answer it on another paired device that can approve, such as your phone. The footer under the buttons says "Approving signs with Windows Hello on this PC, and so does denying."
Some resources only accept approvals from a key that's kept in secure hardware and asks for your fingerprint or face every time. A Windows Hello key doesn't meet that today, so on those Windows says "This credential needs a key with a fingerprint or face check that's kept in secure hardware", names your devices that have one, and offers only Deny. A phone whose key doesn't ask for a fingerprint or face shows the same notice, with Approve turned off.
From 0.5.7, a resource can also require a hardware key that checks it's you each time it's used. Its notice says "This credential needs a key kept in secure hardware that checks it's you each time it's used". See Device keys for the different key rules and the limits of Windows TPM checks.
When you can't approve
| What you see | Why, and what to do |
|---|---|
| Another approver has to approve this | It's your own request (or your own automation's), and the resource needs someone else to approve those. You can still deny it. |
| This request expired | Nobody answered in time. Nothing was granted. The requester can ask again. |
| Already approved, Already denied or Cancelled | Someone answered on another device, or the requester cancelled. Nothing to do. |
| This phone couldn't check this request | What's on screen doesn't match what was asked, so the phone won't approve or deny it. Reopen it. If it still doesn't match, decide on another device or tell your administrator. |
| This phone wouldn't sign it ("This phone couldn't sign it just now"), and trying again doesn't help | The resource may only accept approvals from a key that asks for your fingerprint or face every time. If you paired this phone without Confirm every signature with biometrics, it can't approve that resource. Set up biometric approvals, or approve on another device. You can still deny. |
| This version can't approve it | The request uses something newer than your app. Update the app. |
| Couldn't send your decision | The phone couldn't reach the server. Check your network connection, then try again. |
Problems with the approval key (a locked phone, a cancelled fingerprint check, "Android needs a fresh unlock") are in Troubleshooting.
When a message says "Nothing was approved or denied", that's exactly what happened: your device sends a decision only after it has signed it.