Password expiration warnings are helpful, but they should specify the site they are for. I have a number of different passwords for a training site, a live site, migration site, etc. and all have different passwords. When I get the warning, it just says "Clarity." Would be much more helpful to know which site needs to be updated!

While serving a group of clients within an encampment, data entry could be more efficient if users could record Services snd/or Notes to multiple Encampment members at once.

It's great that Clarity offers so many access rights, which allows customers to create very specific access roles. It would be a great time savings if we could start creating a new access role by duplicating an existing access role and then adjusting the access rights.

System notifications for Updated Referrals and New Referral Notes are sent only to the staff member who created the referral. This is to request that these automated system notifications also be sent to the Staff Member at the Referred-To Program. Notes are also only visible. This would improve communication between different teams and save referred-to agencies from clicking through each client on the referral list checking for updates.

I would like to propose a CLS notification for Street Outreach & ES projects every 90 days, to ensure that clients are not dormant in the system and they are tracked accurately to reflect their updated housing condition.

In order to clean up our Coordinated Entry and Community Queue data, we sometimes need to re-enter/edit/backdate referrals. Our COC analyzes metrics like time between referral date to housing, referral date to program entry, etc. and applying the current system date when adding a referral isn't always accurate.

We are now using multiple queues and for users who work with queues it would be better for them to default to the queue that we determine, as well as to be able to order the queues in the way we designate. There is something clunky about user experience of having to look at the names of the queues and click on the one that you want to use -- having it default to a main queue and also having the order of the queues be meaningful will help in this area.

Create a System Label that acts as a banner to reminds end users to view ROI language and enter the correct dates on start and end date fields.

In Looker, there are currently tables for entry data, status update data, and most recent data (labelled "update/exit" but pulls data for all clients regardless whether updates or exits exist). Please add a table for exit data. Yes, one can use the update/exit and filter it down to exited clients but that can't be combined with active clients without a merged look. E.g. Something as simple as:

ClientID - Entry date - Exit date - Income at entry - Income at exit

requires a merged look to avoid returning "income at exit" for clients who are not exited.

Update the 'Exit' to say 'Program Exit' to make it more clear. Right now it looks like it was an after thought and it is just to xxit the file.

require veteranentered and veteranseparated to be restricted to no more than 4 integers

When scanning in or adding clients in the Attendance module, have an actual pop up appear for those who have a public alert.

Currently, an icon will appear next to the client's name and then you must hover over the client name and then click on the public alert to see it.

This causes delays for shelters that need to check in a large number of clients.

An immediate pop up would ensure that End Users have the ability to both quickly check many people in AND catch important public alerts.

Agencies and communities are required to provide redacted client records when monitored by HUD. Currently, agency staff print the reports, cross through client PII, scan reports, and submit them to HUD. Often the redaction is insufficient. It would be very awesome if users could choose to pull client-level reports excluding PII to serve this purpose.

Clarity would be so much more robust and flexible if client privacy settings were tied to the client and not the agency. Our community offers clients the ability to revoke consents. We also import data from another system so we are forced to choose between database health (client matching on) or client privacy. All of these issues would be resolved if client privacy was set at the client level vs. the agency.

Implement support for organizations utilizing SSO (SAML, OAuth, OpenID). This would be a great help in securing and managing access.

Users at times enter in start dates that occur after the exit date or vise versa. Similarly, users enter Housing Move-in date that may be outside the enrollment (before start date or after exit date).

While there are canned reports ([DQXX-121] Project Start Date > Project Exit Date, [GNRL-106] Program Roster), a pro-active approach would be better.

Also, include logic that detects if enrollment dates are future dated and either generate an alert or possibly and this as "On/Off" switch for system admins to manage.

When we go in to enter services for a CORE Mobile Outreach client, we would like a drop down menu that we can use to toggle services after entering the service dates and vendors. At the moment, we have to enter each individual service one by one, which is extremely repetitive and time consuming.

Example

Service start date: 1/1/2021 Service end date: 1/1/2021
Vendor: Team A

Services
Toggle slide Emergency supplies
Toggle slide Animal services
Toggle slide DMV

Referrals
Toggle slide Concord Care Center
Toggle slide Warming center

Linkages
Toggle slide HCH Mobile Clinic

Save

The Access Roles page would be more helpful if the number of "Assigned" roles was a drill-down