> ## Documentation Index > Fetch the complete documentation index at: https://crevio.co/docs/llms.txt > Use this file to discover all available pages before exploring further. # Vault > Save the logins, cards, and contact info Crevio uses on websites. It fills them straight into the website, so the password or card number never appears in the chat. **Crevio can sign in to websites for you without the password ever appearing in the chat.** You save a login once. When Crevio needs to sign in, it fills the password straight into the sign-in page -- never into the chat or its memory. The same works for payment cards and contact info like your name, address, and phone number. You'll find everything in your vault, under **Settings** > **Vault**. ## Why you'd use it * **A tool you use has no connection to Crevio.** If a person can sign in to it, Crevio can too. * **You don't want to hand over the screen every time.** Without a saved login, Crevio has to stop and ask you to sign in yourself. With one, it carries on. * **You want Crevio to have its own accounts.** Crevio can sign up for a site with a password nobody ever sees, and keep using that account later. ## Save a login **1. Open your vault** Go to **Settings** > **Vault**, click **New item**, and choose **Login**. **2. Fill in the login** Enter a name, the email or username, and the password. **3. Add the website** Enter the web address of the site, like `https://findstack.com`. Crevio only ever fills this login into that exact address. **4. Save** Click **Save**. Next time Crevio meets that site's sign-in page, it uses the login on its own. You can also save a login from the chat. When Crevio reaches a sign-in page it has no login for, it shows a small form right in the conversation. Type the email and password there and click **Save** -- the form sends them straight to your vault, not into the chat. A login saved this way is yours alone (see below). Click **Not now** and Crevio carries on without signing in. This form only appears in the chat inside your dashboard, not in Slack, Telegram, or Discord. ## Import logins from a CSV file Already keep your passwords in your browser or a password manager? Bring them over in one go. **1. Export your passwords** Export them as a CSV file from Chrome, Edge, Safari, Firefox, 1Password, Bitwarden, LastPass, or Dashlane. **2. Import the file** In **Settings** > **Vault**, click **New item** > **Import from CSV...**, choose the file, pick who can use the logins, and click **Import**. **3. Delete the file** The CSV file holds your passwords in plain text. Delete it once the import is done. Rows without a password or a website are skipped, and so is any login already in your vault for the same username and website. Authenticator keys in the file come along too. The import takes logins only -- add cards and contact info by hand. You can also connect 1Password directly, so Crevio uses the logins you keep there without copying them: click **New item** > **Connect 1Password...** and follow the steps. Crevio lists your 1Password logins when you connect and again each time you click **Sync** on the connection. The password and two-factor code are read from 1Password at the moment a login is used, so a changed password works right away, and removing a website from a login in 1Password stops it being used there straight away. > [!NOTE] > > Saved passwords are write-only. Once saved, nobody can see a password again -- not you, not your team, not Crevio. To change one, type the new password when you edit the login; leaving the field blank keeps the current one. ## Two-factor codes If a site asks for a code after the password, Crevio can enter it in two ways: * **An authenticator key.** When you turn on two-factor sign-in on a site, it shows a setup key or QR code for your authenticator app. Paste that key (or the `otpauth://` link) into the login's **Authenticator key** field, and Crevio generates the code itself, the same way your authenticator app does. * **A code sent by email.** If the site emails the code to one of your Crevio inboxes, Crevio reads it from the newest message that arrived in the last 15 minutes. Codes sent by text message to your phone, passkeys, and "approve this sign-in" prompts in an app can't be handled this way. For those, Crevio hands you the screen so you can finish that step yourself. ## Let Crevio create its own accounts When you ask Crevio to sign up for something -- a review site, a directory, a free tool -- it can create the account with a strong password it makes up on the spot. The password is saved straight to your vault, bound to that website, before the sign-up form ever sees it. Nobody sees it, and Crevio signs back in with it whenever it needs to. ## Cards and contact info Save a payment card or contact info the same way: click **New item** and choose **Card** or **Contact info**. Crevio fills contact info into shipping forms the way your browser's own autofill does. For a card, Crevio picks out the card fields on the checkout page, including card forms from payment providers that sit inside the page, and types the card into them. The card number and security code never appear in the chat: Crevio only ever sees the last four digits. Filling a card doesn't place the order -- Crevio still checks the order on screen before it pays. **The first time Crevio fills a card on a website, an admin approves it.** You get an approval card in the chat naming the card and the website, and the payment provider whose card form sits in the page. After you approve, Crevio fills that card on that website without asking again. Only an admin can approve a card -- in Slack, Discord, or Telegram too. Contact info fills without asking. To have Crevio ask again on a website, open the card in **Settings** > **Vault** and remove the website under **Websites approved for this card**. Crevio fills a card only into secure (https) pages. It refuses a form that would put the card number in the page address, or a page where it ran its own code, and it can't run its own code in a page while a filled card is on it. Logins fill without asking, and only on the websites they are saved for. Crevio also refuses to fill a password into a form that would put it in the page address, or into a page where it ran its own code, so nothing else on the page can pick the password up. After Crevio fills a login, the conversation shows a card with the website, the email or username it used, and dots in place of the password or code. The password itself is never shown. A login Crevio just saved is marked **Saved to vault**. You can leave the website blank on a card or contact info, so it can be used on any site. Logins always need a website. ## Find something in your vault The tabs at the top filter by type -- **All**, **Logins**, **Cards**, or **Contact info** -- and show how many of each you have. Type in **Search vault** to find an item by name, username, or website. ## Keep a login to yourself Every saved item is either for the **Whole team** or **Just me** -- the same choice you make when you connect an app. * **Whole team** -- the default when you add something in **Settings**. Crevio can use it in anyone's chats and in scheduled tasks. * **Just me** -- only your own chats can use it. Nobody else on the account sees it, other admins included. Scheduled tasks don't run as you, so they can't use it either -- save a login for the whole team if a task needs it. A login you type into the save form in a chat is saved as **Just me**. To share it, open it in **Settings** > **Vault** and switch it to **Whole team**. Logins Crevio creates for its own sign-ups are saved for the whole team. ## Choose which bots can use it If you have more than one bot, you can also decide which of them gets each saved item: * **All agents** -- the default when you add something in **Settings**. Every bot can use it. * **Only certain bots** -- pick them in the item's settings. Other bots don't see it at all. A login saved from a bot's chat, or one a bot created for itself, belongs to that bot only. Change it in **Settings** > **Vault** if you want to share it. ## What it can't do * **It only fills the exact website you saved.** `https://github.com` doesn't cover `https://gist.github.com`, and a site with and without `www.` counts as two. This is by design: a password can never be filled into a look-alike page. Add each address the sign-in happens on -- a login can have up to 10. * **It only works on websites.** Crevio fills saved items into pages in its own browser. It can't type a password into a desktop program. * **It can't show you a saved password.** There is no "reveal" -- keep your own copy in your usual password manager. * **Once filled, the website has it.** Filling a password into a site is the same as typing it there yourself. Only save logins for sites you trust. * **You can save up to 500 items per account.** ## If something goes wrong * **Crevio says the page isn't one of the saved sites.** The sign-in page lives on a different address than the one you saved -- for example `login.example.com` instead of `example.com`. Open the login in **Settings** > **Vault** and add that address. * **The sign-in fails.** The saved password is out of date. Edit the login, type the current password, and ask Crevio to try again. * **Crevio can't find a verification code.** If the site just sent it, give it half a minute and ask Crevio to try again. If the code went to your phone, Crevio hands you the screen instead. * **The save form in the chat stopped working.** It stays open for 30 minutes. After that, ask Crevio to sign in again and it shows a fresh one, or add the login in **Settings** > **Vault**. ## Related > [card] [Create with AI](https://crevio.co/docs/features/creating-with-ai.md) > > How Crevio works on its own computer, and when it hands you the screen. > [card] [Your account & settings](https://crevio.co/docs/features/settings.md) > > Everything else under Settings. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.