In this guide
When Access Boston will not open, first identify which stage failed: account/password, multi-factor verification, a browser session, or a specific application after sign-in. The City’s FAQ describes single sign-on and repeated MFA prompts caused by browser settings; its help materials direct unresolved account problems to a Service/Help Desk. Use the official portal and the City’s official help page for account-specific action.
This guide does not promise a password-reset shortcut because public instructions can change and reset options depend on the current City setup. It explains what can be checked safely and when to stop guessing.
Pin down the exact failure
Note whether the rejection occurs before the portal opens, during MFA, or only after selecting an application. A wrong password, an unavailable phone, and an application-approval message point to different owners. The distinction is useful even if the screen uses a generic error; record the wording without copying hidden account details.
Try one careful check of the official address, keyboard layout, and any required City username format shown in current onboarding information. Avoid repeated guesses after an account lockout warning. Do not share a temporary password with a supervisor or support agent by ordinary email unless the official process explicitly requires a secure method.
Change is different from recovery
The City welcome guide revised in 2021 describes a Change My Password link inside the Access Boston portal’s Account Tools section for users who can already access the portal. That is an authenticated password change, not proof of a current recovery process for someone locked out. If you cannot reach the account tools, ask your department Service/Help Desk for the current recovery route.
A guide that tells you to use a signed-in password-change link cannot establish that a password reset is available to every user from a public page. Avoid trusting unofficial pages that ask for City credentials or claim they can unlock an account. The first-time setup article covers a temporary password during onboarding; it is a separate situation.
If MFA keeps restarting
The City FAQ last updated October 2, 2023 explains that a browser set to clear session cookies may trigger a new MFA code on each visit. It also flags browser settings that block all cookies. Check only the official portal’s site-level storage behavior, and ask IT before changing a managed device or lowering privacy protections broadly.
If the prompt repeats on one browser but not another, tell IT the browser and whether the issue begins after a new session. Do not send a security code to the help desk as proof; follow the verification method it provides. For a changed or lost phone, see the dedicated MFA device guide.
Signing out can end more than one session
The City’s 2023 Access Boston FAQ says the portal uses single sign-on and that logging out of one application can log you out of the other applications in the same sign-on session. That behavior does not necessarily mean an account was deleted or a password changed. Follow the sign-out prompt and close the browser if the official screen asks you to confirm the logout.
If you need a fresh session, return through the official portal and sign in again using the normal City flow. On a shared or public computer, use the full sign-out process and close the browser. Do not rely on simply closing one tab to end a session, and do not leave a City account open on a device you do not control.
When the portal opens but a tile does not
A missing application after a successful sign-in is an access or approval issue, not necessarily a login failure. The City FAQ explains that some applications require approval and that tile changes can follow a department or role change. Check with your supervisor or application owner and use the missing-application guide.
If the issue is actually an HR case, payroll record, or personal information in another system, identify that system before filing another access ticket. The Access Boston, Beacon and ESS comparison maps those destinations; the support guide explains where to route the issue.
What to include in an official help request
Give the service desk the date and approximate time, the stage that failed, your device and browser, and a brief non-sensitive description. If you have an error code, send it only through the verified City support route. Do not include passwords, MFA codes, Social Security numbers, or screenshots that expose private account data.
If a colleague sends a reset link, verify it through a known City directory or official help page before opening it. This publication cannot inspect messages, validate a reset token, or contact the City on your behalf. For the overall map and official starting point, return to the Access Boston guide.
Official sources and limits
- Access Boston FAQ (updated October 2, 2023)
- Access Boston welcome information (revised May 4, 2021)
- Access Boston Portal Help
Source check: 2026-09-27. The cited City documents have different publication or revision dates; time-sensitive instructions are identified in the guide. Follow the current official portal or your department’s instructions if they differ.