## Overview GitLab Duo will support a new **Always on** availability mode that locks Duo on for all users within a scope, preventing group, subgroup, and project owners from disabling it. This is symmetrical to the existing **Always off** mode — closing a long-standing gap where administrators could lock Duo off but not lock it on. ## Problem Group, subgroup, and project owners can currently override Duo availability settings independently. For enterprises with centralized AI governance requirements — such as compliance teams or regulated industries — this makes it impossible to guarantee consistent AI tooling across the organization. There is no way to mandate that Duo remains available in all namespaces. ## What will be built - A new **Always on** option in the GitLab Duo availability settings, available at the instance level (self-managed) and top-level group level (GitLab.com) - When set, Duo is locked on for all subgroups and projects within that scope - Owners of subgroups and projects cannot override the setting to disable Duo - The option appears alongside the existing Always off, On by default, and Off by default options in the settings UI ## Important notes - Setting availability to **Always on** does not automatically enable experiment and beta features — those must be turned on separately - On GitLab.com, the **Always on** mode is set by the top-level group Owner - On GitLab Self-Managed, the **Always on** mode is set by an Administrator ## Documentation https://docs.gitlab.com/user/gitlab_duo/turn_on_off/ > [!important] > This page may contain information related to upcoming products, features and functionality. > It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. > Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.