We continue to run up on issues where agency level data sharing settings do not allow us the flexibility to share or not share program level data with the CoC. This is my vote for project level sharing settings.

Commenting in hopes that this is reviewed/considered again. With a growing number of primary and behavioral health programs requiring HMIS, we need a more refined way of protecting client data. Staffing at agencies is more fluid than Clarity allows and most agencies also have dozens of programs. As soon as an agency has 2 or more restricted projects and 3 or more employees where the employees need access to different combinations of those projects you can't rely on departments to maintain privacy.

I believe the way a department works is by limiting access to programs to only those users who have that program's department. Any program not in a department will still be accessible to all users. For example, Agency A can have 1 department for program A and all the other programs not in a department. Agency user A with department A will be the only user with access to program A as well as having access to the rest of the other agency programs. However, if all programs in an agency are departments, then users will need access to those departments. As noted by Adele Campbell, the issue here is that users can not have more than 1 department. I think a better fix would be to allow for multiple departments per user vs. creating a new agency...

This seems a very important feature - if a staff at an agency, is assigned to a program Dept., and they still need access to all programs at that agency they are not able to view or edit them.

Program Level Sharing. Multiple departments for users and programs. Currently there is not a way to assign a user a department, ( assigned to one program) and the user have access to all programs in the agency. Communities have to create additional agencies for restricted access, even though it is the same agency, due to department limitations.