UX: GitLab Duo Chat is disabled or not available in GitLab
Context
In &13782 (closed), we are adding fine-grained configuration options to turn off Duo features in groups and projects.
This issue described the expected behavior of the GitLab Duo Chat button in GitLab depending on the availability of the chat.
Problem to solve
Users who normally have access to GitLab Duo Chat should understand why Chat is not available to them in some cases.
Definition of done
- User who has access to GitLab Duo Chat is currently in a group or project where AI features are disabled by admin see a disabled button indicating disabled chat. Disabled button has crossed out Tanuki icon.
- When clicking on the disabled button they see a tooltip
- The tooltip has slightly different UI copy depending if they are in a group or project
- Keyboard shortcut to open the chat is also disabled
- On narrow viewports the disabled button becomes icon-only
| Disabled button | Upon click (project) | Upon click (group) | Narrow viewport |
|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
Which button is shown when? (FYI only)
The scope of this issue is showing the disabled state only. However, these tables show the entire logic of when the button is shown, and in which state, for reference.
This table is for user with access to Duo Chat
- Before paid cut-off: user is a member of a premium or ultimate org and Duo features are allowed at the instance level
- After paid cut-off: user has a Duo Pro seat
| Case | Button type | Issue |
|---|---|---|
| User is in GitLab project where AI features are disabled by admin | Disabled button | This issue |
| User is in GitLab project where AI features are enabled by admin | Enabled button | No action needed |
| User is viewing a GitLab project in a different org (e.g. org is on free tier, org is on ultimate tier and hasn't disabled AI...) | Enabled button | #464559 (closed) |
| User is viewing a page outside of a group or project | No button | #447543 (closed) |
Edited by Katie Macoy



