6 results found
-
Report: Which clients don't have release of information (ROI) on file and/or who have ROI renewals coming up.
With the requirement to upload ROIs for every client, it would be extremely helpful to be able to run a report and see which clients in a given program are due for a renewal or need an initial ROI uploaded. Checking each client individually is a huge waste of staff time when you have thousands of people to check.
2 votesThank you for your feedback. We are in the planning phase of a feature or update related to this item.
-
Allow for manual removal of clients from encampments.
Users have expressed scenarios when automations will not prompt the removal of a client from the outreach map when appropriate. Allowing users this ability will account for the scenarios in which automations are applicable.
22 votesThank you for your feedback. We are in the planning phase of a feature or update related to this item.
-
Multi-select fields should be available on system/agency level
Currently, multi-select fields are only available to be set up by BitFocus. Instead, system admins need to use multiple checkbox fields for each option. Typically, select-all-that-apply questions have many, many choices (even when those questions are designed well and thoughtfully). This quickly eats into custom field limits and custom field publishing to data analysis (both of which are very bad design elements themselves). Please improve this.
26 votesThank you for your feedback. We are in the planning phase of a feature or update related to this item.
-
Allow agencies that operate programs across multiple CoCs to have access to multiple CoCs Community Queues
Some agencies operate programs across multiple HUD CoCs; the agency can only be assigned to a single CoC, but its programs can be assigned to multiple CoCs. Access to a CoC's Coordinated Entry Community Queue is based on the CoC assigned at the agency level, not the CoC(s) assigned at the program level. This prevents programs that operate in other CoC(s) to view the Community Queue(s) for the CoC(s) they operate in.
If an implementation has their Coordinated Entry Type set to "Continuum of Care Based" in their system settings, they should be able to allow agencies that operate programs…
32 votesThank you for your feedback. We are in the planning phase of a feature or update related to this item.
-
Manage Module needs specific access role permissions
For "Enterprise" users, we can choose exactly what permissions our users have for each tab in the client profile and enrollment pages. For the Agency Manager's "Manage" module, you get it all with no limits. Two examples: 1) We would like to be able to assign an Agency Manager that is not allowed to edit programs. 2) We would like an Agency Manager that can add/edit Services and add/edit Accounts, but nothing else.
8 votesThank you for your feedback. We are in the planning phase of a feature or update related to this item.
-
Audit Log Enhancements
Here are some of the things we would like to see in an audit log:
Audit log similar to client audit log (full history) for user accounts (last edits, values changed, additional agency access added/removed, email changed, photo changed, etc)
Agency audit log for changes to address, active status, creation date.
Program audit log in the same vein with history (who changed what and when on a program - the name, the funding, the beds, basically every PDDE change/edit/creation)
Service audit logs (who created them, edited them, changed available dates, active/inactive, etc.)
Sharing settings - audit history on sharing settings.…10 votesThank you for your feedback. We are in the planning phase of a feature or update related to this item.
- Don't see your idea?