Restrict can_delete_contact permission to specific hierarchy for role

@michael Unfortunately still no change this side.

  1. Removed count_visits from ALL contact types:
  2. Made sure NO users have can_view_last_visited_date
    image
  3. We never had any “uhc settings” set in the first place
  4. I even removed the can_view_uhc_stats just to be sure
    image

As can be seen below, the results are still the same:


Going off the code, the original decision to lean into that functionality was made quite a while ago, and as a result, the reasoning is somewhat foggy.
However, it was hoped that the visit count would be tallied for the households. The intention was to draw attention to less-visited households by placing them at the top of the list.

While reading the documentation again I investigated our app forms and found that none of them implement the visited_contact_uuid field. Thank you for drawing attention to it.

Given the lack of uhc settings, and our forms lacking the visited_contact_uuid field, leads me to believe that at the time the team did not really have a thorough understanding of the feature, or perhaps a solid spec/requirement list from our stakeholders, when this was implemented.


How many households are typically in a Plot?

That can differ greatly. A plot/dwelling/location by us is anything from a piece of land, to a block of flats. Which makes it quite a pain point to try and make sure the CHW enumerates all the inhabitable “households” in that place.