# OMB M-26-18: Login.gov as the sign-on for federal public services, explained

OMB’s memorandum of August 31, 2026 requires agencies to offer Login.gov on every in-scope public website with sign-in, to use its identity verification by default, and to phase out other solutions that fit none of its exceptions. Deployment deadlines run one to two years.

Explainer · Government · Customer & Citizen Experience. Published November 14, 2026. Last reviewed November 14, 2026.

## At a glance

- Issued by OMB on August 31, 2026 to the heads of executive departments and agencies, citing Executive Order 14338 on better design.
- Scope: public-facing agency websites where members of the public sign in to services. Sites used only by organizations or by people acting for someone else are out of scope, though agencies may extend Login.gov to them.
- Agencies must offer Login.gov as a sign-on option on all in-scope sites, and use its identity verification where verification is needed, unless it does not meet a service’s specific requirements.
- Other identity solutions may stay only for use cases Login.gov cannot meet or to avoid burdening a large group of existing users; the rest are phased out.
- An agency that cannot meet a deadline sends OMB a notice with a personal certification from the agency head, shared with the required congressional committees.
- Deadlines run from 60 days (an inventory of sites with sign-in) to two years (Login.gov on every in-scope site).

## What the memorandum does

OMB Memorandum M-26-18, *Scaling Use of Login.gov to Deliver a Universal Sign-on for Public Services*, is dated August 31, 2026 and signed by OMB Director Russell T. Vought. It ties back to Executive Order 14338, *Improving Our Nation Through Better Design*, of August 21, 2025 [1].

The memo’s diagnosis is that agencies, lacking a government-wide strategy, built different digital identity solutions. People keep several sign-ons for different agencies, agencies verify the same person again at significant cost, and agencies pay commercial vendors to verify attributes the government may already hold in an official source. The memo’s answer is to enforce Login.gov, the single sign-on platform built by the General Services Administration (GSA), as the universal sign-on for public services online [1].

## Which websites are in scope

The memo applies to all agencies as defined in 44 U.S.C. 3502(1), and to public-facing websites where members of the public authenticate to reach a service. “Public-facing” means meant for the public, not for federal employees or contractors acting for an agency [1].

Two kinds of site are excluded: those used only by organizations or people acting for an organization, such as businesses and state and local governments, and those used only by individuals acting on behalf of another individual. Agencies may still extend Login.gov to those sites and to other channels such as mobile apps. The statutory mandate and its certification requirement do not apply to the Department of War, national security systems or the intelligence community, though the Department of War is encouraged to offer Login.gov where practicable [1].

## Four requirements

### Offer Login.gov for sign-in

Citing 6 U.S.C. 1523(b)(1)(D), the memo states that agencies must offer Login.gov as a sign-on option on every in-scope website. Where a service serves individuals acting for themselves as well as organizations or third-party representatives, Login.gov is required for the individuals and optional for the others. Agencies should follow GSA’s best practices when they implement it [1].

### Use Login.gov to verify identity

Where a site needs identity verification as well as sign-in, agencies must use Login.gov’s verification service unless they determine it does not meet requirements specific to the service’s users, risk profile or operations. The memo uses “identity verification” as an umbrella term, synonymous with identity proofing under NIST SP 800-63-4 [1] [2].

### Keep other solutions only for a reason

Agencies may offer other sign-in or verification options alongside Login.gov in two cases: to meet use cases Login.gov cannot fully meet, such as particular user populations, and to avoid burdening a significant population of existing users. The memo’s examples of harder-to-verify groups are young people and people living abroad, who may have limited official records. Solutions that fit neither case must be phased out [1].

Where other options remain, agencies must promote Login.gov as the default for new accounts for any group it can serve, and must seek to maximize parity in assurance level selection between Login.gov and the alternatives. Agencies should review the need for each alternative regularly, including its volume of active users. The memo supersedes section V.5 of OMB M-19-17, which had pointed agencies to federal or commercial shared services for public identity [1].

### Accept credentials already verified

Agencies that use Login.gov for verification should accept all suitable Login.gov offerings at the Identity Assurance Level they set for a service. Where they need more anti-fraud controls, they should add those inside their own system boundary when practical, not reject Login.gov credentials outright. Login.gov, in turn, should maintain an independent assessment of its credential processes [1].

## Customer experience as part of risk management

The memo puts user burden inside the risk decision. When deciding whether to require verification and at what assurance level, agencies must consider the effect on users and avoid friction the risk does not justify, and must document those decisions. They must monitor their identity programs on an ongoing basis, and the memo names pass rates, abandonment rates and completion time as useful measures, to be read alongside fraud, security and privacy measures [1].

It also asks agencies, with the user’s consent and consistent with law, to use information passed by Login.gov to fill in account details and pre-populate forms, while weighing privacy risks where data was given for a different purpose [1].

## Deadlines

The appendix states each deadline as a period without naming its start date [1].

- **Within 60 days:** agencies report to OMB an inventory of all existing public-facing websites with authentication, coordinated by the agency CIO.
- **Within 240 days:** agencies run a Digital Identity Risk Management process, including assurance level selection, under NIST SP 800-63-4, for public-facing services with authentication or verification.
- **Within one year:** agencies adopt, to the extent practicable, the practices in GSA’s Login.gov implementation guide, and deploy Login.gov on all existing in-scope websites of OMB-designated High Impact Service Provider services, or send OMB the notice.
- **Within 18 months:** agencies with those High Impact Service Provider services report user volumes and performance metrics for Login.gov and any other solution on those sites.
- **Within two years:** Login.gov on all existing in-scope websites, or the notice to OMB.

The notice must name the operational requirements that prevent compliance, include a personal certification from the agency head that meets 6 U.S.C. 1523(b)(2), and be shared with the required congressional committees [1].

GSA and NIST have tasks too. GSA convenes an agency customer cohort within 90 days and at least quarterly after, and within 180 days publishes the implementation guide with OMB, holds an industry day and reports to OMB on ideas such as verifiable digital credentials. Within one year it explores new offerings with NIST, such as accepting credentials from commercial providers. NIST publishes a risk management resource for SP 800-63-4 within 120 days [1].

Status as checked on November 14, 2026. Whether a particular site is in scope, and whether a notice is the right course, are decisions for each agency and its counsel.

Moraph’s teams help organizations with work like this: [see our solutions](https://www.moraph.com/solutions).

## Sources

1. Office of Management and Budget. M-26-18, Scaling Use of Login.gov to Deliver a Universal Sign-on for Public Services (August 31, 2026). <https://www.whitehouse.gov/wp-content/uploads/2026/08/M-26-18-Scaling-Use-of-Login.gov-to-Deliver-a-Universal-Sign-on-for-Public-Services.pdf> Checked November 14, 2026.
2. National Institute of Standards and Technology. NIST SP 800-63, Digital Identity Guidelines (Revision 4). <https://pages.nist.gov/800-63-4/> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/omb-m-26-18-login-gov-public-sign-on-explained>
Publisher: Moraph Insights
