Instance-Level Model Selection Configuration incorrectly restricted to Duo Enterprise only

Summary

Instance-Level Model Selection Configuration for Self-Managed and Dedicated instances using GitLab.com AIG/WFS is currently only visible to Duo Enterprise users, but according to Epic 19144, it should be available to all Duo users including Core and Pro tiers.

Steps to reproduce

1. Access a Self-Managed GitLab instance with Duo Core or Pro license
2. Navigate to Admin Area > GitLab Duo
3. Look for GitLab Duo Model Selection options

Example Project

Any Self-Managed or Dedicated GitLab instance with Duo Core or Pro license

What is the current bug behavior?

Instance-Level Model Selection Configuration is only visible to Duo Enterprise users. Users with Duo Core or Pro licenses cannot access this feature in the admin settings.

What is the expected correct behavior?

According to Epic 19144, Instance-Level Model Selection Configuration should be available to all Duo users regardless of tier:

• Duo Core
• Duo Pro
• Duo Enterprise

The epic specifically states: "Model selection will be available to all Duo users, regardless of tier."

Relevant logs and/or screenshots

Enterprise

Pro

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.