MyCSF should display the scoring weights that are in use for the assessment object on the assessment page to avoid confusion around which weights are being utilized.

Use different contrasting colors for the two options below, please.

Response Status: External Assessor Review Complete
Response Status: External Assessor Review Pending

Unique IDs should be apparent throughout MyCSF and within all reports and analytic tools. For example, a user should not have the click on the "Expand" button within the Assessment to view the unique IDs. Unique IDs should also be available when linking documents, rather than trying to match up the statement language. All reports and analytic tools should reference unique IDs when presenting material by requirement statement.

A search bar present in the "Assessment" page which searches the entire assessment for the given search term. The only search capability currently present are in the documents repository, and it only searches the document descriptions and document names. This new assessment-wide search should consider:
- customer comments
- assessor comments
- requirement IDs
- requirement statements
- document names
- document descriptions
- CAP responses
- diary entries
- scoping factor responses
- (pretty much everything entered in an assessment)

In the modal accessible from the general documents page used to show the requirement statements that are linked to a particular document, the requirement statement text should be a hyperlink leading to that requirement statement. See pic.

When possible, authoritative sources should always appear as hyperlinks to the source itself. For example, anytime we show "NIST 800-53 R4 Control A-20" as a source, it should be presented at a link to https://nvd.nist.gov/800-53/Rev4/control/AC-20. These links should appear when authoritative sources are presented in the "References" section in the tool as well as within the sources presented in the "More Info > Authoritative Sources" window specific to the individual requirement statements.

It would be helpful to have spell checking for the comments section, similar to how it is already implemented for this ideas submission field. If there already is spell checking, then it is not working in my Firefox browser.

with the increased usage of MyCSF by non-US based users all dates should be switched to Month DD, YYYY format from the MM/DD/YYYY format currently used to avoid confusion

When HITRUST reverts an submitted assessment back to either an assessor or to the subscriber, MyCSF should have a field available for HITRUST to state why the assessment was reverted. This field should be required, and this field's contents should be made visible to the subscriber and assessor.

When populating an assessment, MyCSF should offer comment fields for each control maturity level instead of just having one big comment field for the whole requirement. See attached pic.

Add spellcheck functionality.

Ability to visualize the linked documents with the requirement statement without needing to click on the linked documents button. The button to link the documents is an appropriate control for performing the linking function but if the user is able to view the list of linked documents content without another key click, it would expedite data entry QC.

The top menubar containing the Home, Library, Analytics, etc. links should remain visible at all times (even after scrolling down a page).

Ability for an Organization to select what locale (Americas, Europe, and Asia) to where their data is hosted.

Allow a user to change the language presented in MyCSF

Possibly localization depending on User's browser setting