In https://gitlab.com/gitlab-org/gitlab/-/issues/441486 we'll be introducing logic to disable AI features on groups and projects that explicitly disable them. At present, this leads to UX quirks we need to address, such as error messages appearing in the wrong visual elements (see https://gitlab.com/gitlab-org/gitlab/-/merge_requests/145333#screenshots-or-screen-recordings for some examples). We should also consider improvements like hiding UI elements for projects/groups with AI disabled. # Definition of done Do not show the AI feature in the UI if the user will not be able to use the feature. For example:  #### Why? Summarizing a thread in [Slack](https://gitlab.slack.com/archives/CLW71KM96/p1709690682370829) with the designers, basically the user could run into multiple instances of "sorry this feature is not available for whatever reason" which adds noise to the UI. Imagine AI features that the user may regularly run into - they would see the same notification/affordance in the UI repeatedly, interrupting their workflow. # Next steps (:rotating_light: outside of scope for this issue :rotating_light:) I'm writing the next steps as a FYI only, everything that follows is not expected to be completed as part of this issue! How do we let the end user why they can/can't access AI features? This [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/432293 "[Add-On] User should know if they have code suggestions seat provisioned in GitLab") touches upon this for code suggestions, but we could extend that issue to be a bit more holistic. Something along the lines of: * A notification that informs the user they have gained/lost a Duo Pro seat and what that means * A place for the user to proactively check their access to AI, or the projects AI permissions These are loose ideas, but it would be good to come up with something less obtrusive than a feature-by-feature UI affordance. This work will be detailed in this [epic](https://gitlab.com/groups/gitlab-org/-/epics/13246 "Configuration options and access to AI features"). That epic is a follow-up to this issue.