Vault

The Vault is where a credential belongs when no first-class Integration covers the service — an API with no connector, or a site an AI Employee has to sign in to.

A retired connector's secret is already here. Upgrading to 1.132.0 moved each one into a restricted secure note named <Connector> (retired Integration), holding the connector's configuration, and removed the dead Connection. Company owners and admins can Reveal it; the only step left is sharing it, or granting it to the AI Employees that were using the connector.

Add a Vault item

1. Open Vault from the company navigation and choose Add item.
2. Choose Login, API key, or Secure note. Add a clear title and the fields that belong to that type. Login and API-key items can also carry a website and private context.
3. For a login, paste an existing password or choose Generate strong password. Copy a generated password before saving when you also need to enter it somewhere outside Genosyn.
4. Optionally attach an authenticator by pasting its Base32 setup key or complete otpauth:// URI. Leave the field blank while editing to keep the current authenticator. Software passkeys are created from an AI Employee's Browser flow, not imported through this form.
5. Choose whether every Member in the company may view the item or only selected Members may. Save it, then open Access to add people or AI Employees.

The list and detail screens show the title, username, website, type, private context, and whether a login has authenticator codes or passkeys only to Members who can access the item. The stored password, API key, or secure-note body stays masked until someone explicitly chooses Reveal or Copy. A current authenticator code is generated only when someone chooses Show or Copy code, and auto-hides when it expires. Editing never loads an existing password or authenticator setup key into the form; leave either field blank to keep it.

Vault sources (Bitwarden and Vaultwarden)

If the company already runs Bitwarden or Vaultwarden, do not keep those credentials in two places. An owner or admin opens Vault, chooses Integrations in the sidebar, and picks Bitwarden: its Logins and Secure notes are mirrored into this list, where they can be shared with Members and granted to AI Employees like any other item. Genosyn stores only each item's title, username, and website; the password is fetched from Bitwarden at the moment it is revealed, copied, or typed into a sign-in form. Nothing is ever written back — editing and rotating stay in Bitwarden, and the next sync brings the change across.

A mirrored item is marked mirrored from its source and cannot be edited or deleted here. Everything else on this page — Access, Grants, Reveal, Browser autofill, audit — behaves exactly as it does for a native item. The full walkthrough, including the Bitwarden API key that avoids two-step login and what happens on disconnect, is on Vault sources.

Member access

A Vault item has either Everyone in the company visibility or Only selected Members visibility. Restricted items are absent from other Members' lists instead of advertising that a hidden credential exists. The creator and company owners or admins can always manage sharing and deletion.

View

Open the item, read its encrypted metadata and private context, and deliberately reveal or copy the stored value.

Edit

Everything in View, plus change fields and replace the stored value. It does not confer sharing or deletion control.

Company-wide visibility affects Members only. It never gives an AI Employee access. Every AI Employee starts with no Vault access and needs a separate item-level Grant.

AI Employee Grants

Open a Vault item's Access panel and add only the AI Employees that need it. Grants are independent per item, so access to one GitHub login does not expose another login or anything else in the company Vault.

Use

Discover safe item metadata. For a Login, use server-side Browser autofill for its username, password, or current authenticator code without returning plaintext to the model, or use one of its software passkeys in Genosyn's browser. Passwords and codes go only into matching sign-in inputs, and passkey private keys never cross the browser boundary. API-key values and secure-note bodies have no AI plaintext-read or Browser-fill path.

Manage

Everything in Use, plus update a login's title, username, and private context. The saved website origin cannot be rebound by an AI Employee. Manage also cannot reveal, rotate, or delete the stored password, authenticator setup key, or passkey material. A login an employee creates receives this level automatically, which also lets it capture authenticators during that signup flow.

With Manage, update_vault_login can change the title, username, or private context while preserving the encrypted credentials and saved website origin. Website rebinding, password rotation, authenticator removal, passkey deletion, and login deletion remain deliberate Member actions in the Vault.

Sign in without showing the model a password

With the built-in Browser enabled, an AI Employee can complete a login without asking a Member to paste a password into Chat:

1. list_vault_items returns only granted item ids and safe metadata, including whether a Login has an authenticator or passkeys. It never returns a password, setup key, current code, passkey private key, API key, or secure-note body.
2. The employee opens the website saved on the login item.
3. browser_fill_vault asks the App to resolve a granted username, password, or current authenticator code and fill the selected field directly in App-owned Chrome. The top page and target frame must both match the item's exact saved origin — scheme, host, and port. A password is accepted only into type=password; a current code is generated at the last possible moment and goes only into an ordinary sign-in input.
4. For passkey sign-in, browser_use_vault_passkey loads only the selected origin-bound credential into Genosyn's software authenticator. The site performs its normal WebAuthn assertion and the updated signature counter returns to encrypted storage.

Browser access and the employee's host allow list remain independent gates: a Vault Grant cannot enable the Browser or widen its browsing policy. Sensitive values exist only at the server-side credential-to-browser boundary. They are not serialized into the tool response, model context, Run transcript, audit detail, or log. Captchas, hardware-bound credentials, and unsupported challenges can still use the Browser's human take-over flow.

Browser snapshots redact password-input values, including values inside frames, before the model sees them. After the session has observed or filled a password, model-requested screenshots are refused; use the redacted structural snapshot instead.

Let an AI Employee create a login safely

AI Employees can store new credentials without first learning the password in model context. create_vault_login generates a strong password inside Genosyn, encrypts it immediately, creates a company-visible login, and gives the creating employee a Manage Grant. Members can therefore recover the credential, while other AI Employees still receive no access. The employee can then use browser_fill_vault to enter that generated value into a signup or password-change form.

When a website or browser flow already put a password into an input, browser_save_vault_login can request capture from a same-origin password input. Capture always needs approval from a company owner or admin, even when ordinary Browser form submissions do not require approval. Once approved, the App saves a restricted Vault item bound to the exact current origin and gives the employee a Manage Grant. The password is not read back or included in model output. Other Members do not see the restricted item until an owner or admin changes its visibility or Member access.

During authenticator enrollment, browser_prepare_vault_totp first binds an AI-created Login to the exact origin and redacts screenshots and model-visible page text before the secret appears. browser_save_vault_totp then reads the selected same-origin setup key, authenticator QR image, or containing element. Genosyn validates and encrypts it server-side. Later, browser_fill_vault with the totp field generates and fills a current code without returning the setup key or code. For approval-gated forms, browser_submit_with_vault_totp generates that code only after Approval is claimed and submits it immediately. A QR format Genosyn cannot decode still needs take-over or manual setup-key entry in the Vault editor.

Passkeys use bounded Browser ceremonies. browser_create_vault_passkey triggers the selected registration control, captures and encrypts the resulting credential, and removes the temporary authenticator before returning. browser_use_vault_passkey similarly restores one granted credential only for the selected sign-in action, saves its updated counter, and removes it before returning. These tools are refused in Member browsers and never access Touch ID, Face ID, a password-manager passkey, or a hardware security key.

Reveal, copy, and audit

Revealing and copying are separate, explicit Member actions. Each one writes a company audit event identifying the Member, Vault item, action, and time, without recording the secret itself. Creating, updating, deleting, sharing, granting, and AI use are audited too. Review the history under Settings → Audit log when investigating access or rotating a credential.

• Do not paste a Vault value into Chat; Grant the item and use a governed action.
• Save the intended website origin on login items. Browser autofill requires the top page and target frame to match its scheme, host, and port exactly.
• Back up the whole data directory so the database and any managed instance-secret file stay together. Rotating security.encryptionSecret follows the same key-ring procedure as other encrypted company data.