Restricting record visibility by user in a Tracker program

Thanks for the like @elmoujarrade !

I received a tip from one of my colleagues that it might not be a good idea to create all the several programs as it might cause challenges when the data is to be analyzed by those in the above OUs.

In fact, it does seem like others have included this request before, so I’ll be looking for the similar requests in the community to share with the team. Other community members are welcome to add their input here as well.

If I remember correctly, in one of those community posts, it was suggested to create a sub OU for each data entry (maybe a better suggestion that the program for each user :sweat_smile:)… would that work? @elmoujarrade , maybe this post will be helpful if you choose this path: Best approach for OUs where CHWs come and go - #2 by Jim_Grace

Thanks!

1 Like