Docs: Clarify GitLab Duo Code Review capabilities for unlicensed users

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem to solve

The current GitLab Duo in merge requests documentation does not clearly explain which Duo Code Review capabilities are available to unlicensed users versus users with a GitLab Duo license. This creates confusion for:

  • Administrators deciding how to roll out Duo
  • Users who can see Duo suggestions but don't understand why they can't interact with them
  • Sales/CS teams explaining the value proposition of Duo licensing

Further details

What unlicensed users CAN do:

  • View Duo code suggestions in merge requests
  • Upvote or downvote Duo suggestions
  • Apply Duo suggestions to their MR

What unlicensed users CANNOT do:

  • Ask for feedback within a Duo MR thread review (no response received)
  • Mention @GitLabDuo and receive a response
  • Add GitLab Duo as a reviewer on a merge request
  • Benefit from project-wide automatic Duo MR review settings (attempting to create an MR with automatic code review enabled results in an error message for unlicensed users)

Proposal

Add a section to the Duo in merge requests documentation that clearly outlines:

  • A table or list showing licensed vs. unlicensed user capabilities
  • Expected behavior/error messages unlicensed users will see when attempting restricted actions
  • Clarification that project-wide automatic review settings require licensed users

This could be added as a new subsection titled "License requirements for Duo Code Review features" or integrated into existing feature descriptions with clearer availability callouts.

Who can address the issue

Technical Writer for the Duo/AI-powered features group, with input from the Duo Code Review PM/Engineering team for accuracy verification.

Other links/references

Edited by Michael Balzer