You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, these guardians are unable to create new accounts to manage their Veteran’s affairs and existing users will lose access to their MHV accounts where they currently manage the Veteran affairs once MHV is deprecated Jan 31, 2025. There is no pathway to create an account for guardians through the modern credentialing systems (Login.gov and ID.me).
Short-term:
Retain MHV functionality for existing guardians.
Update the VA.gov sign-in page to:
Remove the MHV button.
Add a link for court-appointed guardians to access their existing accounts.
Out of Scope for Short-term solution:
Developing or implementing a process for new guardians to create accounts.
Product name: Sign-in experience
Team name: OCTO Identity Experience
OCTO product owner: Samara Strauss
Product manager: Joelle Wells
Slack channel: #secure-sign-in-transition
Dedicated content writer on your team (if you have one): Megan Driscoll
Timeline
Need to launch by 2/1/25, and it seems like they're breaking this into multiple pieces that are going through staging separately?
IA Support
Acceptance Criteria
Strategy for guardian access pre 2/1 is documented in our IA mural for future use
Competitive research on delegate accounts
Early strategic thinking for future of guardian experience, including guardian account creation. Multiple design directions/options.
Review with Mikki
The text was updated successfully, but these errors were encountered:
Overview
Description
Currently, these guardians are unable to create new accounts to manage their Veteran’s affairs and existing users will lose access to their MHV accounts where they currently manage the Veteran affairs once MHV is deprecated Jan 31, 2025. There is no pathway to create an account for guardians through the modern credentialing systems (Login.gov and ID.me).
Short-term:
Out of Scope for Short-term solution:
Links
Team
Product name: Sign-in experience
Team name: OCTO Identity Experience
OCTO product owner: Samara Strauss
Product manager: Joelle Wells
Slack channel: #secure-sign-in-transition
Dedicated content writer on your team (if you have one): Megan Driscoll
Timeline
Need to launch by 2/1/25, and it seems like they're breaking this into multiple pieces that are going through staging separately?
IA Support
Acceptance Criteria
The text was updated successfully, but these errors were encountered: