# Restrict app forms to user types

**URL:** <https://forum.communityhealthtoolkit.org/t/restrict-app-forms-to-user-types/2195>\
**Category:** Technical Support\
**Created:** [September 22, 2022, 6:42pm UTC](https://forum.communityhealthtoolkit.org/t/restrict-app-forms-to-user-types/2195 "2022-09-22T18:42:21Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![binod](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/binod/32/60_2.png) [@binod](https://forum.communityhealthtoolkit.org/u/binod)\
**Post date:** [September 23, 2022, 7:34am UTC](https://forum.communityhealthtoolkit.org/t/restrict-app-forms-to-user-types/2195/3 "2022-09-23T07:34:05Z")

</div>

To add to @jkuester’s answer above:

It might not be immediately clear that the `user` properties being referenced in the form expression are actually sourced from the user’s associated contact document.

For example, if your user’s role (visible in the user management) is `chw`, but the associated contact does not have a field named `role` with value `chw`, it will not work as expected. In that case, please make sure that you have the correct `role` in the contact document too.

---

_[View the full topic](https://forum.communityhealthtoolkit.org/t/restrict-app-forms-to-user-types/2195)._