New navigation item: GitLab Duo

Proposal

Add a navigation on .com for GitLab Duo add-on management, separating it from the Usage Quotas page:

Image	Description
	Move UI that is currently behind a tab on (Top-level group): Settings>Usage Quotas
	Entire UI that is currently behind a tab on Usage Quotas gets its own page

Rationale own navigation item:

• GitLab Duo add-on is an important initiative for GitLab, therefore it's important that it is highly discoverable
• "Usage quotas" is a mixture of many things, and isn't an intuitive place to find GitLab Duo configuration

Rationale own page:

• GitLab Duo is getting more complex, with a second add-on coming soon.
• GitLab Duo configuration options are also growing
• Having a single page gives the space this feature needs for all configuration options

Full rationale in epic

Other locations that were considered

Image	Desc	Why not this?
	Leave as is	This functionality is intermixed and buried on a page that isn't an intuitive place for this functionality, the feature is not discoverable
	Build functionality into settings, which would open a new page for seat management (v. rough design)	Buries important functionality into our already very crowded settings

Validation

Evidence of problem

Discoverability

• "It took me an embarrassingly long time to find the page again. I didn’t look at documentation because I thought I should be able to find it myself in the UI." - heuristic eval
• "🤔 I want to add AI features; how do I do it?" - heuristic eval
• "I would expect to see AI related section in Settings, but there is only a checkbox in Features section..It would be great to have one page for enabling, buying, setting up the Duo" - heuristic eval
• "The toggles were clear, but it did take me a while to find the GitLab Duo Pro tab." - heuristic eval

Confused by relationship of seat management and other Duo settings

• "Developers told me they couldn’t access experimental features. I mistakenly thought that everything would be enabled for them after turning all the toggles on in “Usage Quotas” - heuristic eval
• (From settings) "Wait, what’s this about Code Suggestions? Isn’t that already enbaled?" - heuristic eval
• "I disabled Duo features, but I'm not sure if I will pay for it or not. It's not clear that I need to enforce the disabling to actually disable Duo features. It's not clear what a regular disabling option does." - heuristic eval

JTBD

Does this navigation proposal facilitate one of our primary JTBDs? Which job?
Buy a development lifecycle tool to increase efficiencies

How does this change improve the workflow for users attempting to complete that job?

• Minimize the time it takes to acquire a development lifecycle management system
• Discoverability of feature
• Reduces friction/steps to invite users to tool and manage permissions of tool

Checklist

• Review the handbook page for navigation.
• 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.
• Add relevant designs to the Design Management area of the issue.
• Ensure your UI suggestion align with the Documentation Style Guide.
• Engage Technical Writing. They can help craft a term that best describes the feature(s) you’re proposing.
• Follow the product development workflow 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.
• Engage the Foundations Product Manager 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, 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.

Requirements

• Add a new Settings > GitLab Duo navigation item for top-level groups on dotcom
• This page should render the content currently shown on the Settings > Usage Quotas > GitLab Duo tab
• The Settings > Usage Quotas > GitLab Duo tab should not change. We are showing this content in two places to support different usage patterns.
• Do not change Duo Seat management for self-managed instances (Admin Area > GitLab Duo Pro)

Follow-up items

• Add page title and subtitle. Refer to the this thread for more info: !156951 (comment 1963942957).
• Remove the feature flag.
  • Document the new location (https://docs.gitlab.com/ee/subscriptions/subscription-add-ons.html#for-gitlabcom).
  • Update redirects from group_usage_quotas_path(<namespace>, anchor: 'code-suggestions-usage-tab') to group_settings_gitlab_duo_usage_index_path(<namespace>).