# How to configure the new Contextual Kee buttons

**URL:** <https://forum.kee.pm/t/how-to-configure-the-new-contextual-kee-buttons/278>\
**Category:** Uncategorized\
**Created:** [November 20, 2017, 9:20pm UTC](https://forum.kee.pm/t/how-to-configure-the-new-contextual-kee-buttons/278 "2017-11-20T21:20:43Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![luckyrat](https://forum.kee.pm/user_avatar/forum.kee.pm/luckyrat/32/10_2.png) [@luckyrat](https://forum.kee.pm/u/luckyrat)\
**Post date:** [January 8, 2018, 10:51pm UTC](https://forum.kee.pm/t/how-to-configure-the-new-contextual-kee-buttons/278/8 "2018-01-08T22:51:36Z")

</div>

The issue below is potentially related. Needs more planning to establish if there should be independent configurability for the contextual button and form filling but we need to at least consider the overlap.

> [@Potential feature: Ignore some fields](https://forum.kee.pm/t/potential-feature-ignore-some-fields/561):
>
> Needs more detailed use cases and specification. When logging in using forms with some basic captcha functionality or other fields that change with every login operation, Kee will consider the login entry as different to any others already stored in the database and hence, unless disabled by configuration, will ask the user to save the new password. Could come up with a blacklist/whitelist system? With pre-populated magic names? (what? “captcha”? etc.) Also worth thinking about context - e.g.…

---

_[View the full topic](https://forum.kee.pm/t/how-to-configure-the-new-contextual-kee-buttons/278)._
