Skip to main content
U.S. flag

An official website of the United States government

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

State, local, and territories

Crises, like the COVID-19 global pandemic and ongoing natural disasters, make it more urgent than ever for the public to gain fast and easy access to their benefits and services. The General Services Administration’s (GSA) Technology Transformation Services (TTS) realizes the burden this has put on state and local governments. Our team, with deep expertise in security, product, engineering, and user experience, is seeking state, local, and territory government partners that want to take advantage of all that Login.gov has to offer.

Our team, with deep expertise in security, product, engineering, and user experience, is seeking state and local government partners that want to take advantage of all that Login.gov has to offer for their federally funded programs. TTS must limit engagements with state and local entities to work that is linked to federal programs in which TTS is uniquely positioned to provide assistance. As such, your program must be federally funded or linked to a federal program such as the United States Digital Services (USDS).

Steps to partnership

  1. Introductions and determine compatibility

    During the introduction call, an account manager will walk through Login.gov services and answer any questions that you have. This step will determine if Login.gov is a good fit for your agency. Contact our Partnerships Team to get started.

  2. Estimate usage and test integrations

    During onboarding, an account manager will work with your organization to estimate usage and provide a cost estimator. Once you’ve created your application and implemented an identity protocol, you can register it in the test environment dashboard and start testing. We advise at least two to three weeks for your team to test and integrate with Login.gov. Learn more about the sandbox environment.

  3. Establish an Intergovernmental Cooperation Act (IGCA) agreement

    Login.gov is a cost-recoverable federal service, which means we must, by law, charge for our work. Our partnership and financial engagement will be governed by an Intergovernmental Cooperation Act (IGCA) agreement. An IGCA agreement is a contract between a federal agency and a non-federal entity, like a state or local government. For Login.gov, these are the contracts we have with state, local, and territory governments that let them use Login.gov as partners/clients. Learn more about the IGCA process below.

  4. Launch integration

    Once testing is complete and the IGCA agreement has been executed, Login.gov aims to launch your integration within two weeks. We recommend a grace period between deployment and implementation on your site.

Social Security Administration

“The SSA UXG team appreciates the willingness of the Login.gov team to listen to our goals, concerns, and questions, then work with us to identify a path forward that will benefit the customers (end users) of SSA and other federal agencies. The team’s flexibility and willingness to hear our suggestions is very much appreciated. We enjoy brainstorming together and sharing research findings as we try to help each other move forward.”

Elizabeth Hanst
Former Technology Lead User Experience Specialist
Social Security Administration

Intergovernmental Cooperation Act (IGCA) agreement process

Tips for completing the IGCA agreement process:

  • Determine your executive for the IGCA agreement sign-off
  • Have approved funding access based on the cost estimator
  • Ensure your technical team has capacity for integration or plan to hire a team

The above suggestions may help keep your agency on track for creating the IGCA agreement and receiving proper approvals.

  1. IGCA agreement request form

    Partner entity works with Login.gov to make an IGCA agreement request letter, which requires signature by the executive of the entity (the governor of a state, mayor of a city, or designated governmental official delegated from the chief of the executive).

  2. IGCA agreement and Scope Of Work (SOW)

    Partner entity works with Login.gov on an IGCA agreement outlining the SOW.

  3. IGCA agreement creation

    TTS performs a review with GSA counsel, and returns the IGCA agreement to the partner entity ready for signatures.

  4. Partner approval

    Partner reviews, agrees, and routes the IGCA agreement for signatures to return to TTS.

  5. GSA approval

    GSA approves and finalizes the IGCA agreement and returns finalized documents to the partner.