What do you like best about CredentialStream?
The automation is excellent. Pre-CredentialStream, our process was close to 100% manual, primarily relying on spreadsheets to track data and assignments, as well as other software to communicate with providers, and verifications were pulled manually and saved as PDFs using Adobe Acrobat. CredentialStream takes all of these steps and makes an automated process in many ways, or allows us to conduct all of these job functions in a single place. It frees up time for Cred Reps to focus on more complex issues and getting their work across the finish line.
I am also very happy with the overall consistency of the system's reporting capabilities. No matter what type of report you want to run, you must build a query, then build a report, and then attach the two together. No exceptions. It's simple and unchanging, and the repetition makes committing this to memory much easier and faster. So much of CredentialStream's advantages over other products lie in its ability to report on a vast variety of data, but the process of generating a report is always three steps: build a query, build a report, and attach them together. The simplicity cannot be overstated for both new and long-time users, and the consistency and easy-to-learn process builds reliability. And reports can be automated, so both of my "likes" go together. Review collected by and hosted on G2.com.
What do you dislike about CredentialStream?
The thing I dislike the most about CredentialStream is the audit trail. It is very difficult to read and identify what fields are being changed, and it doesn't cover User and Group settings at all. The audit trail requires a look-back range (ex. 04/01/2023 - 04/14/2023) and shows all changes made during that window. The results are formatted in a table.
The table is unfortunately not set to automatically resize, meaning I always need to scroll to the right to see every column, most of which are far too wide for the data that is actually present, so I actually need to scroll because of the large amount of blank space within the column widths.
Additionally, the fields are in the computer coding syntax the software engineers use to actually code the system rather than the name of the field that users see. These require me to know the coded name of the field rather than the field I can see in the system. For example, if I need to see a change to a Workflow, the audit trail defines this as "DR_CHK" This infers the field is a Checklist (an outdated function) but it's actually the Workflow. There are no guides available to users to define each field we see by its computer code, which means a user just has to figure out what the name means through trial and error. The field name in the audit should match the name of the field the user can see, since users will be primarily using the audit trail to track changes in their company's version of the system.
Finally, there is no audit trail for changes made to User and Group settings, which seems like an oversight in my opinion. Verity Support also confirmed this was not a feature with the system, but could be suggested to the Developers via the Thrive community. We have had issues with permissions changing from week to week by someone other than our super-users, but without an audit trail for User and Group settings we are unable to determine if system updates are removing permissions or if a user is. Being able to audit changes made to User and Group settings is a very basic function the system should have, especially when there's an audit trail for virtually every other area.
I would very much like the audit trail cleaned up to automatically resize column widths based on the data the audit trail logs, a frozen column header line, and all computer coding syntax replaced with the actual names of the fields that viewers see, as well as an expansion to cover User and Group settings changes. Review collected by and hosted on G2.com.
