## Summary Give Group Owners one place to see and finish Duo agent and flow setup for their group, mirroring the project-level card shipped under the [DAP Project Readiness Dashboard epic](https://gitlab.com/groups/gitlab-org/-/epics/22591). Requested by Kai (@phikai) in [team-ops work item 45](https://gitlab.com/gitlab-com/ai-engineering/ai-coding/team-ops/-/work_items/45). ## Design source of truth [Group prototype](https://pajamas-prototyping-kit-fe3fa0.gitlab.io/#/duo-onboarding-group). All scope and copy below reflect this prototype; anything unsettled is an open point in [629951](https://gitlab.com/gitlab-org/gitlab/-/work_items/629951). The redesign lives on branch `akozovski/duo-onboarding-tweaks` (commit `2a288324`) in the pajamas-prototyping-kit project; it is not merged, has no MR, and the Pages URL above still shows the earlier design. See [629951](https://gitlab.com/gitlab-org/gitlab/-/work_items/629951) for the request to publish an MR. ## Surfaces | Surface | Location | Notes | |---|---|---| | GitLab.com top-level group | Settings > GitLab Duo > Configuration | Only place with the Agent Platform switch, Seatless access, and the membership table | | GitLab.com subgroup | Settings > General | Inherited and locked from the top-level group, same cascade as the project card | | Self-managed | Settings > General | No Configuration page; Agent Platform belongs to an administrator | Placement, to confirm in [629952](https://gitlab.com/gitlab-org/gitlab/-/work_items/629952): the sections mount once in the shared group AI settings form. The header replaces the "Configuration" heading there and renders at the top of the General block's content. ## Page structure No card. Settings > GitLab Duo opens directly on six sections: 1. Agent and flow setup: four counted steps (GitLab Duo, Agent Platform, Agents, Flow execution), each with nested detail rows. 2. Additional context: GitLab Orbit, External MCP tools, IDE access. Not counted. 3. User permissions: minimum role for CI/CD-pipeline features, minimum role for other features. 4. Restrict access based on group membership: the membership table, or, on a subgroup or self-managed instance, a line naming who can change it. 5. Local setup: unchanged, moved before Other GitLab Duo settings. 6. Other GitLab Duo settings: availability table, code review customization, data privacy, kept flat. Every setting is a row in the section it belongs to and appears exactly once; a control an ancestor namespace or the instance has locked is inert with a lock icon, and a control whose own parent step is off is muted and keeps its value, except Foundational flows and Custom flows, which show off. ## Feature flag Ships behind `duo_group_agent_readiness_settings` (wip), separate from the project card's `duo_agent_readiness_settings`. Rollout issue: [630145](https://gitlab.com/gitlab-org/gitlab/-/work_items/630145). ## Relationship to other work Mirrors [DAP Project Readiness Dashboard](https://gitlab.com/groups/gitlab-org/-/epics/22591). The External MCP tools row shares its GraphQL field design with the project-level [629943](https://gitlab.com/gitlab-org/gitlab/-/work_items/629943). ## Breakdown and scope - [ ] [Group readiness: finalize the design prototype](https://gitlab.com/gitlab-org/gitlab/-/work_items/629951) - [ ] [Group readiness: placement, IA, and scope decision](https://gitlab.com/gitlab-org/gitlab/-/work_items/629952) - [ ] [[Feature flag] Rollout of `duo_group_agent_readiness_settings`](https://gitlab.com/gitlab-org/gitlab/-/work_items/630145) - [x] [Group readiness: shared row components](https://gitlab.com/gitlab-org/gitlab/-/work_items/630146) - [ ] [Group readiness: Agent and flow setup section](https://gitlab.com/gitlab-org/gitlab/-/work_items/629953) - [ ] [Group readiness: group runner row](https://gitlab.com/gitlab-org/gitlab/-/work_items/629954) - [ ] [Group readiness: GitLab Orbit row](https://gitlab.com/gitlab-org/gitlab/-/work_items/629955) - [ ] [Group readiness: MCP tools rows](https://gitlab.com/gitlab-org/gitlab/-/work_items/629956) - [ ] [Group readiness: remaining settings sections](https://gitlab.com/gitlab-org/gitlab/-/work_items/630147) Most of the prototype's lower page is a rearrangement of existing group Duo settings, not new functionality. Scope will likely shrink relative to the prototype. Engineering: Tian (@tgao3701908), Mike (@mikewronski). Design: @akozovski, @aregnery. ## Definition of done - [ ] Every setting appears exactly once, on either the Configuration page or the General block. - [ ] The four step counters and the state line agree with the rows underneath them. - [ ] Group runner and connected MCP servers load after first paint; a failed check shows retry copy on its own row and never becomes an error state. - [ ] Every row saves through the existing group settings form and endpoint. - [ ] Documentation covers the group sections; the flag is enabled by default and removed per [630145](https://gitlab.com/gitlab-org/gitlab/-/work_items/630145).