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
- Browse the Library
- View a value
- Edit a credential's values
- Expire and replace a value
- Expire now or schedule expiry
- Save a replacement
- View an old value
- Make your own credential
- The fields each type starts with
- Changing the type
- Change or end sharing
- "Always approved"
- Hidden and shown values while you type
- If you switch apps while typing
- Privacy settings
- Hide values when switching apps
- Allow screenshots
- What the apps can't do yet
View, save and share credentials
The Library tab lists the credentials you may ask for, approve or own, in folders. Depending on how your server is set up, you can also view a credential's value, save new values into it, and make your own credentials to share.
All of this is off until your administrator turns it on for a resource. If you don't see an option described here, that's the likely reason.
Browse the Library
- Open Library. Credentials are grouped in folders; ones without a folder are under Unfiled. Credentials others shared with you are under Shared with me.
- Search the library looks at names, descriptions and folders, never at values.
- Tap a credential for its Details: type, folder, description, who issues it, how long each token lasts, the longest access you can ask for, and Your access.
Your access says where you stand, for example No grant, Waiting for approval, "Active · 42 min left", or You approve this. From there you can Request access, Request again, or Open request.
These ownership and sharing labels are from 0.5.7. In 0.5.6 and earlier, Shared by followed by a name gives the credential's owner, and the other labels described here do not appear.
The small icons and labels beside each credential tell you separate facts:
- Owned by you or Owned by alice names the owner. Something you own can also say Shared with others.
- Shared by bob names the person who last changed the sharing that gives you access, if your role lets you see who that was. Owners and Managers may see who else shared it. Viewers and Editors see only the owner's name, so the app doesn't repeat it beside Owned by alice.
- Shared directly with you, or Via and a group's name (for example Via family), says how you have access. Sharing with a group doesn't make the group the owner. The credential's Sharing section lists every way you have access, and your role.
- Config-managed means the credential comes from your administrator's server configuration. It has no individual owner.
Some roles can't see who shared an item, and older servers don't say. The app then shows only how you have access, and doesn't guess. Ownership unavailable means the server didn't say who owns the item.
A folder's labels sum up the credentials you can see in it, including those in folders inside it. Mixed ownership means they have different owners, or are managed in different ways; the folder itself still has no owner. A folder says Ownership unavailable if the server didn't say who owns any one of them. Folders only organise credentials; they don't give anyone access. Ownership and sharing labels are separate from who approves requests, from your role, and from whether a grant has ended or been revoked.
View a value
Viewing is the one place the app shows a secret. Your administrator turns it on per resource, in one of two ways: for people who hold an active read grant for it, or for its approvers.
- Open the credential in the Library (or in Grants, under Secrets you have access to).
- Read the warning: "Anyone who sees this value has it. Viewing can't be undone."
- Tap Show value. The key uses its normal check: a standard Android key only needs the phone unlocked; a biometric key asks for fingerprint or face, and a Windows Hello key asks for Windows Hello. The device signs the view, and your server records it in the log ("Viewed prod-db-password").
- The value hides again after 30 seconds, or when you leave Bouncer. Tap Hide to hide it sooner.
Copy puts the value on the clipboard, and Bouncer clears it from the clipboard after 30 seconds, if it's still there. How safe copying is depends on the device:
- Android: the copy is marked sensitive, so Android doesn't show it in its clipboard preview. The clearing only happens while Bouncer is still running: if you close Bouncer, or Android stops it, within those 30 seconds, the value stays on the clipboard until you copy something else over it.
- Windows, from 0.5.1: the copy is kept out of clipboard history (Win+V) and isn't synced to your other devices by cloud clipboard. Bouncer also clears it when you quit Bouncer and when Windows ends your session (signing out or shutting down). If Bouncer crashes or is ended from Task Manager, it can't clear the copy, and the value stays on the clipboard until you copy something else. If Windows won't take the protected copy, nothing is copied and Bouncer says so.
- Windows, 0.5.0 and earlier: the copy is a plain one. Windows clipboard history and clipboard sync to other devices can keep it after Bouncer clears the clipboard. If you use either, turn them off (Settings > System > Clipboard) before copying a secret, or type it instead, or update to 0.5.1.
On Android and Windows, the screens that show or take a value are protected from screenshots and screen recording in the normal app, unless you turn on Allow screenshots (see Privacy settings).
If you can't view a value, Your access says why:
| Message | Meaning |
|---|---|
| Hidden: "Show and Copy appear once you have an active read grant." | Ask for access first. |
| Viewing is off for this credential | Your administrator hasn't allowed viewing it on a device. Scripts and agents can still use it with a grant. |
| Nothing to show | It's SSH access, which uses a new certificate for each connection. There's no stored value. |
| Your grant only saves values | A save grant lets you save new values, not read them. |
| Nothing is stored yet | The secret store has no value for it yet. Save one first. |
| This grant isn't yours | Only the person who holds a grant can view with it. |
Edit a credential's values
If the button says Replace (new version) rather than Edit, this credential keeps a version history. Use Save a replacement below; its form differs from the one described here.
Where you're allowed to save new values into a credential from this device, its Details screen has an Edit button (from 0.5.2). That's the owner or an Editor of a personal credential, or an approver of a resource your administrator lets you save into. Grants, under Secrets you have access to, opens the same form from a row marked Save. On Windows this needs Windows Hello approvals.
- Open the credential in the Library and tap Edit.
- The fields it already has are listed by name, empty and hidden. Opening the form doesn't fetch anything.
- Type a new value only in the fields you want to change. A field you leave empty keeps its current value: Bouncer sends only the fields you typed in, and the others aren't touched. A field can't be removed here.
- If you may also view the value, Load current values fills the form with what's saved, hidden. It's the same as Show value: you confirm it's you, and the log records it as a view. A loaded value you leave as it was isn't sent again, and loaded values go after 30 seconds, as a shown value does. If you may save but not view, you only replace values, and nothing is fetched.
- Tap Save and confirm it's you. After your fingerprint, face or Windows Hello, Bouncer sends the values once to your organisation's server, which stores them in the secret store. The app doesn't keep them.
- You should see "Saved" and the field names. The log records the save, never the values.
For a personal credential you own, Name, folder and type at the top of the form changes those. A personal credential keeps the fields it was made with, so you can't add new ones. For a resource from your server's configuration, Add a field adds a new field name.
Expire and replace a value
If your administrator has turned on version history (called lifecycle) for a credential or its storage area, its Details has a Versions section. It shows the version in use ("Version N is in use"), whether it has expired or is set to expire, and each older version's state, dates and who made the change. Listing versions doesn't fetch any values. "Saved (date) outside Bouncer" means Bouncer has no record of who saved that version; it doesn't tell you who changed the value.
Verification on 18 November 2026: the operations in these steps were
checked through the server's API with fake data, against a server built
from unreleased source at main commit 79335c2. The steps have not yet been
run in the app itself; button and label names come from the app's source.
Versions arrived in 0.5.3. The device-key checks in this section need 0.5.7 on both the app and the server. Builds from source made before the version bump still report 0.5.6+33, so the version number alone doesn't show whether a build has these checks. Ask your administrator which source commit your app and server were built from.
For a resource from your server's configuration, its approvers can expire it. Replacing it also needs your administrator to allow app saves and self-approval. For a personal credential, its owner, Editors and Managers can expire or replace it.
These changes need a key that checks it's you every time: a biometric key on a phone or Windows Hello. The key must also meet the credential's own key settings. If a button is missing, the reason can be your permissions, this device's key or the installed version. The administrator chapter has the full permission table.
Expire now or schedule expiry
- In Library, open the credential's Details and find Versions.
- Check which version is in use. To stop Bouncer handing out the value now, tap Expire now, read the warning and tap Expire. Confirm it's you when the device asks.
- To expire it later instead, tap Schedule expiry, pick a future date and time, and confirm it's you. Check the scheduled time it shows afterwards. Remove scheduled expiry removes it before it happens. To change the time, remove the schedule, then set a new one.
- Once it has expired, you should see Expired: waiting for a replacement. Bouncer hands nothing out for it, and never uses an older value instead.
The value stays in OpenBao's history. Bouncer tries to revoke the tokens it issued for the value, including tokens it handed out that nobody has used yet, and retries any that fail. Anyone who copied the value still has it, and an API key from another system still works there until it's revoked at that system. Sessions already open don't close. A version's expiry is separate from a grant ending or a standing grant's review date.
Save a replacement
- Open the credential's Details, check Versions, then tap Replace in Versions, or the Replace (new version) button that takes the place of Edit.
- Type a new value in at least one field. A field you leave empty keeps its current value. This form doesn't load the current values; Show shows only what you type.
- Tap Save replacement and confirm it's you.
- You should see "Saved as version N", with the new version number. Check Versions again. The credential keeps its ID, name, folder and sharing, and grants that already exist can use the new value.
If it's refused:
- "This credential changed. Check the current version and try again." Someone changed it while you were editing. Go back to Details, check the version in use and start again.
- A message that a replacement would remove an old version's value for good means OpenBao's version limit would be exceeded. Ask your administrator to review it. The app has no way to approve removing it.
- The server says OpenBao's answer was lost. The save may have worked. Check Versions before you try again. If it worked but Bouncer could not record it, you will see "Saved (date) outside Bouncer", without who saved it. For a personal credential, tokens that were handed out but not yet used may still read the old value, because Bouncer didn't revoke them when OpenBao's answer was lost.
View an old value
Only the owner of a personal credential can view an old version's value, and only where its storage area allows values to be shown. For a resource from your server's configuration, its approvers can, where viewing in the app is turned on. Can reveal the value, given when a credential is shared with you, doesn't cover old versions.
- In Versions, tap View on the older version. It only appears if you're allowed and this device's key is suitable.
- Check the version number and read the warning: "This is an old value, not the one in use. Each view of it is logged on its own."
- Confirm it's you.
The view is signed and logged separately from ordinary views. A value that was deleted, destroyed or removed in OpenBao can't be shown. Viewing an old value doesn't make it the version in use, and doesn't restore access to an expired credential.
Make your own credential
If your server is set up for personal credentials, you can make credentials you own and share them.
- In Library, tap New personal credential.
- Choose what you're adding, such as Password, API key or SSH private key. If none fits, choose Secret bundle / other. Bouncer sets up the usual fields for that type (see the table below). On a server older than 0.5.0 the type still sets up the fields, but it isn't saved.
- Fill in:
- Name: up to 64 standard keyboard characters, kept exactly as typed;
- Folder: where it shows in your Library. Folders only organise; they don't change who can use it. My credentials means no folder;
- Storage area, only if your server has more than one;
- Fields: the type's fields, each with a label and "Saved as" the field name. Fields marked (optional) can be left empty or removed. Add a field adds your own, with a field name and a value.
- Under Access, choose Approval required (you approve each request).
- Under Shared with, Add a person or Add a group by their ID, and choose a role for each: Viewer (can find it and use it), Editor (can also save new values) or Manager (can also share it). Tick Can reveal the value to let them view it. To keep the credential to yourself, don't add anyone under Shared with.
- Tap Review, check You're authorising, then Verify and create and confirm it's you.
- You should see "Created. Only who you chose can use it."
The values go once to your organisation's server, and the app doesn't keep them.
The fields each type starts with
| Type | Fields (optional ones in brackets) |
|---|---|
| Password | (username), password, (url) |
| API key | api_key, (url) |
| Access token | token, (url) |
| Certificate only | certificate, (chain) |
| Certificate + private key | certificate, private_key, (chain), (passphrase) |
| SSH private key | private_key, (public_key), (passphrase) |
| Encryption / signing secret key | secret_key |
| Public / private key pair | private_key, public_key, (passphrase) |
| Recovery / backup codes | recovery_codes, (account), (url) |
| Authenticator / OTP seed | otp_seed, (account), (url) |
| Secret bundle / other | one field you name |
Keys, certificates and recovery codes take several lines, and keep every line exactly as you paste it. Bouncer never trims or changes a value.
Changing the type
You can change the type from the Type row at the top of the form. Everything you've typed stays. If a field you filled in has no place in the new type, Bouncer asks first, and that field stays as one of your own, with the same name and value.
If you see "Personal credentials aren't on yet", your server isn't set up for them; ask your administrator.
Change or end sharing
Open the credential's Details. Under Sharing:
- Change sharing updates who has access. It applies from now on.
- Rename or move changes only its name, folder or type.
- Disable stops everyone using it until you Enable it again.
- Delete removes it.
Disabling or deleting revokes the tokens already handed out where possible, but a value someone already revealed can't be taken back. Change it at its source if that matters.
"Always approved"
The Access choice also offers Always approved, which lets the people you share with use it without asking. Always approved is experimental and may change or be removed, and a server may refuse it. Choose Approval required instead. If you see credentials shared as Always approved, check them with your administrator.
Hidden and shown values while you type
On the create and edit forms, a username, account or website is shown as you type it. A password, private key, token, passphrase, seed or recovery code is hidden. Each hidden value has its own Show button (an eye) to check what you typed; tap it again, or Hide, to hide it. With a keyboard, Tab from the field to the button and press Enter or Space. A screen reader announces it as "Show Password, Hidden" or "Hide Password, Shown".
Show only shows what you typed on this device. It doesn't fetch a saved value or contact your server. A field you add yourself is hidden while you type unless you untick Hide this value as I type.
If you switch apps while typing
From 0.5.2, on Android and Windows, what you've typed stays when you switch to another app or minimise Bouncer, so you can look something up and come back. It's kept only in Bouncer's memory, never saved on the device. Any value you chose to show is hidden again when you come back (unless you turn off Hide values when switching apps, below), and on a phone the form is covered in the app switcher.
What you've typed is cleared when:
- you lock your device, or it locks itself;
- you sign out or switch to another Bouncer server;
- your server stops accepting this device;
- you leave the form and choose Discard. If you've typed anything, leaving asks first;
- Android or Windows closes Bouncer.
On iPhone, what you've typed is cleared whenever Bouncer goes to the background, because the iPhone app can't yet tell switching apps from locking the phone. The Mac app, still in development, does the same.
Privacy settings
Settings has a Privacy group. Its settings are kept on this device only.
Hide values when switching apps
On unless you turn it off.
- On: when you switch away from Bouncer, any value you chose to show (a typed value, or a credential's value from Show value) is hidden again.
- Off: a value you chose to show stays shown when you come back. A credential's value from Show value still hides after its 30 seconds, however long you were away, and isn't fetched again.
Either way, what you've typed is kept as described above, and locking your device, signing out and your server's permissions work exactly the same.
Allow screenshots
On Android and Windows only, and off unless you turn it on.
- Off: the create and edit forms, and a shown value, are kept out of screenshots and screen recordings.
- On: those screens can be captured like any other. A screenshot of a value contains that value, so turn it on only when you need to, and turn it off again afterwards.
Changing it takes effect straight away, even with one of those screens open. It doesn't depend on Hide values when switching apps. If your server records what devices report, a screenshot or recording Bouncer notices on one of those screens is still recorded in History, marked as allowed by this setting. Bouncer says nothing on screen when that happens.
iPhone and Mac don't have this setting: iOS doesn't let an app block screenshots, and it isn't available on the Mac yet. An internal test build doesn't have it either, because it never blocks screenshots.
What the apps can't do yet
Folders can be made, but not renamed, moved or deleted. A credential can be moved to another folder with Rename or move, if it's a personal credential you own.