A Massachusetts HR/CMS problem is not always a password problem.
The Commonwealth publishes specific enterprise system requirements for HR/CMS Employee Self-Service, including supported operating systems, browsers, mobile platforms and accessibility software. The current requirements page was updated March 18, 2026.
Checking those requirements can help distinguish an authentication failure from a browser or workstation problem.
Current Windows and Mac Support
The Commonwealth currently lists HR/CMS Employee Self-Service support for applicable x64 Windows environments including Windows 10 and 11, as well as listed server versions.
For Mac users, current requirements list:
- macOS Ventura 13;
- macOS Sonoma 14;
- macOS Sequoia 15.
These published requirements can change, so an old HR/CMS guide found elsewhere on the web should not automatically be treated as current.
Which Browsers Does HR/CMS Support?
Current Commonwealth enterprise requirements list modern versions of the major browsers for HR/CMS.
Google Chrome
The Commonwealth lists the latest stable Chrome release, including automatically updated versions, for HR/CMS Employee Self-Service.
Mozilla Firefox
Firefox ESR 115, ESR 128 and the latest stable Firefox release are currently listed.
Microsoft Edge
Current requirements list supported Edge versions including Edge 120+, 130+ and 140+.
Safari
Safari 16.x, 17.x and 18.x are currently identified for HR/CMS.
Internet Explorer
Internet Explorer is explicitly marked not supported.
This matters because older HR/CMS instructions still exist online and may reference software that is no longer part of the current supported environment.
Why Old System-Requirement Pages Can Be Misleading
Enterprise applications accumulate documentation over many years.
For example, older Massachusetts HR/CMS documents available online refer to outdated Windows, Safari, Chrome and Internet Explorer versions. The Commonwealth now maintains a newer enterprise requirements page with substantially more recent specifications.
If two guides conflict, use the current official requirements rather than assuming the older document remains authoritative.
That is especially important for browser troubleshooting.
Can HR/CMS Be Used From a Phone?
Current Commonwealth requirements include mobile support.
HR/CMS Employee Self-Service presently lists:
- Android 11 and newer;
- iOS 16;
- iOS 17;
- iOS 18.
The Commonwealth also notes that applicable mobile devices need WebKit capability.
Mobile support does not mean every complex employee workflow will necessarily feel identical to a desktop interface, but a phone or tablet is not automatically an unsupported way to access HR/CMS.
Pop-Up Blockers Can Matter
The Commonwealth’s enterprise requirements contain a detail that is easy to miss: pop-up blockers must be disabled for page help to function properly.
That creates a different class of problem from complete login failure.
If the main application loads but a help function or secondary window does not appear, browser behavior may be responsible.
Before changing security settings broadly, however, confirm that you are on the legitimate Massachusetts government service.
Cached Files Can Create Display Problems
Massachusetts also maintains an official browser-cache guide and links it from the Employee Self-Service resources.
The Commonwealth explains that browsers store local copies of website resources to speed up future visits. When applications or documents are updated, cached copies can sometimes cause an older version to remain visible or create display and access problems.
Clearing the cache can therefore make sense when:
- an official page appears outdated;
- a document does not show its newest version;
- the interface behaves differently after an update;
- a known application page is displaying incorrectly.
It is not a universal fix for every HR/CMS problem.
Cache Problem or Account Problem?
The symptoms are usually different.
Likely Browser or Cache Issue
The official site opens, but a page renders incorrectly, old content persists or a feature fails to display.
Likely Authentication Issue
The official HR/CMS authentication process rejects your credentials or MFA.
Likely Permission Issue
You can sign in successfully but cannot see a function another employee has.
Likely Record or Workflow Issue
You can reach the correct page, but the underlying information or employment action is wrong.
Treating each category differently prevents unnecessary password resets and support requests.
Accessibility Support
HR/CMS also has published accessibility support.
Current enterprise requirements list recent versions of:
- JAWS;
- Dragon Professional;
- Dragon Professional Anywhere;
- ZoomText.
The Commonwealth separately maintains HR/CMS navigation instructions specifically for JAWS screen-reader users.
Within Employee Self-Service, the My Preferences area can also be used to turn an accessibility layout on or off.
This is materially different from ordinary browser compatibility, which is why accessibility support should not be reduced to a generic instruction to “try another browser.”
Do Not Troubleshoot From an Unverified Login Page
Technical troubleshooting only makes sense once you know the destination is legitimate.
The safest starting point remains the official Massachusetts Employee Self-Service resource.
If an unknown page obtained through a search result appears broken, do not start disabling browser protections or entering credentials repeatedly.
First verify that you are using an official Commonwealth route.
Our HR/CMS access and security guide covers that distinction in more detail.
A Better Troubleshooting Sequence
When HR/CMS does not work as expected, use the failure itself to decide the next step.
Page will not render correctly: check the current browser requirements and cache.
A pop-up or help feature will not appear: review browser restrictions and pop-up behavior.
Credentials are rejected: use the official access or password-support process.
A tile is missing: investigate role or permissions.
Employee information is wrong: contact the HR or payroll organization responsible for the underlying record.
This is more effective than assuming every problem is caused by the HR/CMS login.