# Summary The user settings is going through a lot of changes as we are adding more authentication features and improvements (ie. [Passkeys](https://gitlab.com/groups/gitlab-org/-/work_items/19442) and [Mandatory Email Authentication](https://gitlab.com/groups/gitlab-org/-/work_items/18304)). This means the sidebar navigation is bloated with information and could benefit from introducing a flyout menu to everything related to accounts access to improve information architecture, so we propose the following navigation changes: <table> <tr> <th>Before</th> <th>After</th> <th>Summary of changes</th> </tr> <tr> <td> {width="858" height="600"} </td> <td> {width=669 height=600} </td> <td> * Move 6 sidebar items under a flyout menu called `Access`. This wouldn't affect or break existing URLs. * Move "Manage authentication" (which includes 2FA and Passkeys) out of [Account](https://gitlab.com/-/profile/account) page to live in the "Password & authentication" menu since Passkeys are closely related to both Password and 2FA. </td> </tr> </table> # Background **How does this change improve the workflow for users attempting to complete that job?** By reducing cognitive load with the use of an existing pattern in the user settings. **How many users will be impacted by this proposed change?** - [ ] Limited - [ ] Moderate - [x] All users **What is the product maturity stage of the associated feature?** - [ ] Experimental - [ ] Beta - [x] General availability **How often do you expect an average GitLab user (_not_ just your target persona) to reach for this functionality?** - [ ] Several times a day - [ ] Once a day - [ ] A few times a week - [x] Once a week - [x] Less than once a week # Approaches considered Simply not introducing the flyout menu and leaving items in the sidebar. # Justification * **Unmoderated usability testing performed successfully:** During the Authentication vision work designed in Q4 2026 ([Dovetail here](https://gitlab.dovetail.com/projects/1sA5DB2UeIRKyQVT7wnVb8/readme)), 5 users were asked to manage their SSH keys within their GitLab account. Once reaching their user settings, users successfully found SSH keys under the proposed flyout menu. See highlight video below: {width="900" height="562"} * **Familiar existing pattern:** We already use the flyout menu as a familiar pattern in multiple pages of GitLab, including the homepage where we have "Security". * **Scalability:** Introducing a flyout as a menu "Category" helps us scale better for future authentication and access features. * **Reduced cognitive load:** By consolidating 6 related items under "Account access," we'd be reducing visual clutter and making it easier for users to quickly scan and find what they need. * **Predictability:** Grouping authentication-related items (SSH keys, tokens, applications, 2FA, passkeys) under a clear parent category helps users predict where to find these items because they're logically related. * **Preserved URL structure:** The proposed changes do not alter URLs, avoiding technical debt or broken bookmarks. # Review checklist #### Requester - [x] Review the [handbook page for navigation](https://handbook.gitlab.com/handbook/product/ux/navigation/). - [x] Add relevant information to the issue description detailing your proposal, including usage and business drivers. - [ ] List at least two other places you considered to introduce your feature. - [x] Add relevant designs to the Design Management area of the issue. - [ ] Ensure your UI suggestion align with the [Documentation Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide/). - [x] Engage ~&quot;Technical Writing&quot;. They can help craft a term that best describes the feature(s) you’re proposing. - [ ] Follow the [product development workflow](https://handbook.gitlab.com/handbook/product-development-flow/#validation-phase-2-problem-validation) validation process to ensure you are solving a well understood problem and that the proposed change is understandable and non-disruptive to users. Navigation-specific research is mandatory for additions or when restructuring. - [x] Engage the [Foundations Product Manager](https://handbook.gitlab.com/handbook/product/categories/#foundations-group) for approval. The Foundations DRI (@jtucker_gl) will work with UX partners in product design, research, and technical writing, as applicable. - [ ] Consider whether you need to [communicate the change somehow](https://design.gitlab.com/patterns/navigation#messaging-changes-to-users), or if you will have an interim period in the UI where your item will live in more than one place. - [ ] Ensure engineers are familiar with the [implementation steps for navigation](https://docs.gitlab.com/development/navigation_sidebar/#navigation-sidebar). #### Foundations Product Manager - [ ] Confirm proposal has necessary information - [ ] Schedule design review for next milestone #### Foundations Product Designer - [x] Confirm Pajamas guidelines are followed - [~] Confirm a11y needs are addressed - [x] Confirm burden of proof supplied for stated scope of access