> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/user-guides/es/browser-extensions/keeperfill-for-chrome-and-brave.md).

# Instalar en Chrome

Instrucciones de instalación de KeeperFill para Chrome, Brave y otros navegadores basados en Chromium.

### Instalación desde Chrome Web Store

Visite el enlace siguiente para instalar **Keeper Password Manager & Digital Vault** desde Chrome Web Store.

{% embed url="<https://chromewebstore.google.com/detail/keeper%C2%AE-password-manager/bfogiafebfohielmmehodmfbbebbbpei>" %}
Chrome Web Store
{% endembed %}

Para que Keeper quede siempre visible en la barra de herramientas, haga clic en el **icono de rompecabezas** y luego en el **icono de chincheta** junto a Keeper Password Manager.

<figure><img src="https://187056193-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Frp3ylVdg2U6pDdl81oP6%2Fuploads%2Fgit-blob-16e22a97a1fc980065d33e6e9f2016600ddad94a%2FScreen%20Shot%202023-10-10%20at%2011.16.04%20AM%20(1).png?alt=media" alt=""><figcaption><p>Fijar Keeper Password Manager</p></figcaption></figure>

Keeper debe estar habilitado en todos los sitios de forma predeterminada. Para confirmarlo, vaya a la pantalla de opciones de la extensión. El acceso a sitios debe estar habilitado "En todos los sitios".

<figure><img src="https://187056193-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Frp3ylVdg2U6pDdl81oP6%2Fuploads%2Fgit-blob-fe237adbaebf0f7376c5603daa1f0dcd2b044e9a%2FScreen%20Shot%202023-10-10%20at%2011.21.04%20AM.png?alt=media" alt=""><figcaption><p>Keeper habilitado para todos los sitios</p></figcaption></figure>

### Desactivar el administrador de contraseñas integrado de Chrome

Recomendamos que desactive las funciones integradas de guardado de contraseñas de Chrome.

* Vaya a: <chrome://password-manager/settings> y compruebe que todas las funciones de relleno automático estén desactivadas.

<figure><img src="https://187056193-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Frp3ylVdg2U6pDdl81oP6%2Fuploads%2Fgit-blob-dcd4c074804088e22fc4f144b2bb5850898227a0%2FScreen%20Shot%202023-10-10%20at%2011.30.00%20AM.png?alt=media" alt=""><figcaption><p>Funciones de relleno automático del navegador desactivadas</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/user-guides/es/browser-extensions/keeperfill-for-chrome-and-brave.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.