Duo settings move to new Duo page
Problem to solve
We have made many attempts at finding the right balance of customer control and technical complexity over the last 12 months. Lots of decisions were made in isolation to drive a variety of specific behavior in the moment. Now that our features are maturing, we want to streamline and wrap up our approach to AI settings to reduce confusion and make it easy for customers to understand.
In https://gitlab.com/gitlab-org/ux-research/-/issues/3080+ we tested a Duo Settings Concept on a standalone page which housed everything Duo configuration related. This concept tested well and is something we can be confident going forward with.
Intended users
- GitLab Admins and Maintainers
User experience goal
- Users should be able to easily navigate to GitLab Duo Settings.
- Users should be able to configure GitLab Duo for their instance/group, and easily understand how configurations cascade down to sub-groups and projects.
- Users should be able to understand seat assignment, and assign seats as it makes sense.
- The design should be scalable, as we expect to have the need to add more configurations later.
Proposal
- A unified page to see an overview of your Duo Configuration, as well as options to further adjust configurations.
Duo Settings Landing Page
The SSOT for these designs can be found in the below Figma File:
Feature Configuration Page
The SSOT for these designs can be found in the below Figma File:
Seat Utilization Page
The SSOT for these designs can be found in the below Figma File:
Documentation
What does success look like, and how can we measure that?
Is this a cross-stage feature?
-->