Skip to content

Commit

Permalink
Merge pull request #3432 from laurwill/patch-11
Browse files Browse the repository at this point in the history
Update sign-in.md
  • Loading branch information
humancompanion-usds authored Oct 28, 2024
2 parents c47e0de + 14bc19d commit c58d5ce
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions src/_patterns/help-users-to/sign-in.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
layout: pattern
permalink: /patterns/help-users-to/sign-in
sub-section: help-users-to
title: Sign-in
title: Sign in
intro-text: "Follow this pattern to help users sign in to access VA online services."
status: use-with-caution-candidate
research-title: Help users to sign in
Expand Down Expand Up @@ -37,10 +37,11 @@ This pattern works differently depending on the product and the account type a p

**To design and build, follow these steps:**

1. Choose 1 of the 2 blue sign-in alert variations. If a person signs in with a verified account, they should only encounter an initial sign-in alert.
1. Choose 1 of the 2 blue sign-in alert variations to implement, depending on whether your product requires everyone to sign in. These will only show to people who are not yet signed in.

2. Implement both of the yellow verification alerts. If a person signs in with an unverified account, they should encounter 1 of the 2 variations. One is for unverified **Login.gov** and **ID.me** accounts, and one is for unverified **My HealtheVet** accounts.
**Note:** This pattern is currently tailored to products that require verified (LOA3 or IAL2) accounts. If your product accepts unverified (LOA1 or IAL1) accounts, you'll need to adjust the content in the blue sign-in alert. And you won't need to implement the yellow verification alerts. Work with CAIA and the identity team to adjust for your situation.
2. Implement all 3 of the yellow verification alerts. These will only show to people who signed in with an unverified account, depending on which account type they're using (Login.gov, ID.me, or My HealtheVet).

**Note:** This pattern is currently tailored to products that require verified (LOA3 or IAL2) accounts. If your product accepts unverified (LOA1 or IAL1) accounts, you'll need to adjust the content in the blue sign-in alert. And you won't need to implement the yellow verification alerts. Work with CAIA and the identity team to adjust for your situation.

{% include content/sign-in-alert-examples.md %}

Expand Down

0 comments on commit c58d5ce

Please sign in to comment.