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

Although Login.gov was founded to provide digital identity solutions to federal agencies, we’ve since begun to serve a number of state and local partners. That’s because state and local governments face similar challenges when offering digital services to their constituents. Login.gov makes it easy for your constituents to access your services while protecting against cybersecurity threats and fraudulent schemes. In fact, many of them will already have a Login.gov account from their interactions with the Federal Government that they can reuse, making it even easier to do so.

We support a variety of use cases - anywhere from enabling a state-wide enterprise type solution to supporting a single program. And as a Government program, we only serve Government agencies, meaning that we understand and focus on supporting your use cases. We’d love to work with you, regardless of whether your applications are associated with a federal program or funding source.

Please reach out to our partnerships team at partners@login.gov as you have questions.

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.

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.