# Mute inactive CHVs accounts

**URL:** <https://forum.communityhealthtoolkit.org/t/mute-inactive-chvs-accounts/2117>\
**Category:** Implementation\
**Tags:** forms, design\
**Created:** [August 23, 2022, 11:57am UTC](https://forum.communityhealthtoolkit.org/t/mute-inactive-chvs-accounts/2117 "2022-08-23T11:57:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sue](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/sue/32/355_2.png) [@sue](https://forum.communityhealthtoolkit.org/u/sue)\
**Post date:** [August 23, 2022, 11:57am UTC](https://forum.communityhealthtoolkit.org/t/mute-inactive-chvs-accounts/2117/1 "2022-08-23T11:57:11Z")

</div>

In many projects, we have designed and implemented muting workflows for Households and Household members. However, CHV supervisors would also like to mute CHVs before replacements.

1. Have you encountered such a request from your projects’ CHV supervisors?
2. What are some of the reasons/motivation for muting/unmuting CHVs by there supervisors?
3. How do you ensure objective rather than subjective reasons for muting/unmuting CHVs?
4. How does your CHV supervisor manage Households left by dead/relocated CHVs?