Saving passwords and keys for Metir to use
Somewhere to keep the logins and keys Metir needs, so it can sign in to things for you without the value ever being shown back to you or written into a conversation.
Security
Logins and API keys that chat and your Blobs can use
Authentication Methods
Passwords & Keys
Blob access
Blobs get none of it until you say so
- Passwords & Keys lives in the Security tab
- Name it, and set the site it belongs to
- Saved, and never shown back in a conversation
- Blobs get none of it until you say so
Where it lives
Passwords & Keys is in the Security tab of your account settings, under Authentication Methods. Every entry gets a short name, and that name is all the assistant ever sees.
Adding one
Choose Add a credential
Name it something you will recognise, such as Acme login.Pick the type
Login, API key, Token or Secret note.For a login, set the site
A login with a site set can only ever be typed into that site, so a lookalike page cannot collect it. This is the single most useful thing on the form.
Bringing across what you already have
Import from a password manager takes a CSV exported from Chrome, Apple Passwords, Bitwarden or 1Password. The file is read on your own device: you see a list of what it found, keep or drop each entry, and only the ones you keep are sent and stored encrypted. Values are never previewed, not even to you, during the import.
Who can use one
Chat can use a saved credential straight away. Blobs start with none: open an entry, tick the Blobs that should have it, and save. Nothing is granted by default and nothing is granted in bulk. See creating a Blob.
Seeing and changing one
Show value reveals an entry to you, and that reveal is recorded. Each row also shows when it was last used, or that it never has been. Edit replaces the value without changing the name, because the name may already be in use elsewhere.