<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> > [!important] > This page may contain information related to upcoming products, features and functionality. > It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. > Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc. <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> From our design/scope discussions, here is the high level passkey flows planned under this interlocked item. These will be reflected in the child epics/issues, and subsequent revised to 2FA account page or prompting new registering users for Passkeys will be done in future iterations. - For users logging in with GitLab native username/password, prompt them to add a passkey (hero flow). - The prompts should be configurable to ensure they aren't perennially displayed. - New user registrations will be excluded from pass key setup prompt (hero screen) along with existing users being invited to a group would not be prompted during that invite acceptance. - Existing users can also add passkeys as a password replacement by navigating to the Manage password page. - Existing users can add/edit/remove passkeys as a 2FA mechanism in the current Manage 2FA screen