ContextQMD
Back to Gitlabhq

GitLab Duo add-ons

doc/subscriptions/subscription-add-ons.md

18.11.214.4 KB
Original Source

{{< details >}}

  • Tier: Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

{{< history >}}

{{< /history >}}

GitLab Duo add-ons extend your Premium or Ultimate subscription with AI-native features. Use GitLab Duo to help accelerate development workflows, reduce repetitive coding tasks, and gain deeper insights across your projects.

Three add-ons are available: GitLab Duo Core, Pro, and Enterprise.

Each add-on provides access to a set of GitLab Duo features.

GitLab Duo Core

GitLab Duo Core is included automatically if you have:

  • GitLab 18.0 or later.
  • A Premium or Ultimate subscription.

If you are an existing customer from GitLab 17.11 or earlier, you must turn on features for GitLab Duo Core.

If you are a new customer in GitLab 18.0 or later, features for GitLab Duo Core are automatically turned on and no further action is needed.

To view which roles can access GitLab Duo Core, see GitLab Duo group permissions.

GitLab Duo Self-Hosted

If you have an offline license, GitLab Duo Core is not available on GitLab Duo Self-Hosted because GitLab Duo Core requires connection to the GitLab AI Gateway.

If you have an online license, you can use GitLab Duo Core in combination with GitLab Duo Self-Hosted. To use GitLab Duo Core, you must select the GitLab-managed model for GitLab Duo Non-Agentic Chat and Code Suggestions for the instance.

GitLab Duo Core limits

Usage limits, along with the GitLab Terms of Service, apply to Premium and Ultimate customers' use of the included Code Suggestions and GitLab Duo Chat features.

GitLab will provide 30 days prior notice before enforcement of these limits take effect. At that time, organization administrators will have tools to monitor and manage consumption and will be able to purchase additional capacity.

Limits do not apply to GitLab Duo Pro or Enterprise.

GitLab Duo Pro and Enterprise

GitLab Duo Pro and Enterprise require you to purchase seats and assign them to team members. The seat-based model gives you control over feature access and cost management based on your specific team needs.

GitLab Duo Agent Platform Self-Hosted

{{< details >}}

  • Offering: GitLab Self-Managed

{{< /details >}}

{{< history >}}

  • Introduced in GitLab 18.8

{{< /history >}}

Customers with an offline license must purchase the GitLab Duo Agent Platform Self-Hosted add-on to use self-hosted models in the Agent Platform.

Customers with this add-on are billed based on seats instead of usage.

Customers with an online license can use self-hosted models in the Agent Platform without an add-on, and are billed based on usage.

To purchase GitLab Duo Agent Platform Self-Hosted, contact the GitLab Sales team.

Purchase GitLab Duo

To purchase GitLab Duo Enterprise, contact the GitLab Sales team.

To purchase seats for GitLab Duo Pro, use the Customers Portal or contact the GitLab Sales team.

To use the portal:

  1. Sign in to the GitLab Customers Portal.
  2. On the subscription card, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}).
  3. Select Buy GitLab Duo Pro.
  4. Enter the number of seats for GitLab Duo.
  5. Review the Purchase summary section.
  6. From the Payment method dropdown list, select your payment method.
  7. Select Purchase seats.

Purchase additional GitLab Duo seats

You can purchase additional GitLab Duo Pro or GitLab Duo Enterprise seats for your group namespace or GitLab Self-Managed instance. After you complete the purchase, the seats are added to the total number of GitLab Duo seats in your subscription.

Prerequisites:

  • You must purchase the GitLab Duo Pro or GitLab Duo Enterprise add-on.

For GitLab.com

Prerequisites:

  • You must have the Owner role.
  1. In the top bar, select Search or go to and find your group.
  2. Select Settings > GitLab Duo.
  3. By Seat utilization, select Assign seats.
  4. Select Purchase seats.
  5. In the Customers Portal, in the Add additional seats field, enter the number of seats. The amount cannot be higher than the number of seats in the subscription associated with your group namespace.
  6. In the Billing information section, select the payment method from the dropdown list.
  7. Select the Privacy Policy and Terms of Service checkbox.
  8. Select Purchase seats.
  9. Select the GitLab SaaS tab and refresh the page.

For GitLab Self-Managed and GitLab Dedicated

Prerequisites:

  • You must be an administrator.
  1. Sign in to the GitLab Customers Portal.
  2. On the GitLab Duo Pro section of your subscription card select Add seats.
  3. Enter the number of seats. The amount cannot be higher than the number of seats in the subscription.
  4. Review the Purchase summary section.
  5. From the Payment method dropdown list, select your payment method.
  6. Select Purchase seats.

Assign GitLab Duo seats

Prerequisites:

  • You must purchase a GitLab Duo Pro or Enterprise add-on, or have an active GitLab Duo trial.
  • For GitLab Self-Managed and GitLab Dedicated:
    • The GitLab Duo Pro add-on is available in GitLab 16.8 and later.
    • The GitLab Duo Enterprise add-on is only available in GitLab 17.3 and later.

After you purchase GitLab Duo Pro or Enterprise, you can assign seats to users to grant access to the add-on.

For GitLab.com

Prerequisites:

  • You must have the Owner role.

To use GitLab Duo features in any project or group, you must assign the user to a seat in at least one top-level group.

  1. In the top bar, select Search or go to and find your group.
  2. Select Settings > GitLab Duo.
  3. By Seat utilization, select Assign seats.
  4. To the right of the user, turn on the toggle to assign a GitLab Duo seat.

The user is sent a confirmation email.

For GitLab Self-Managed

Prerequisites:

  • You must be an administrator.
  1. In the upper-right corner, select Admin.
  2. In the left sidebar, select GitLab Duo.
    • If the GitLab Duo menu item is not available, synchronize your subscription after purchase:
      1. In the left sidebar, select Subscription.
      2. In Subscription details, to the right of Last sync, select synchronize subscription ({{< icon name="retry" >}}).
  3. By Seat utilization, select Assign seats.
  4. To the right of the user, turn on the toggle to assign a GitLab Duo seat.

The user is sent a confirmation email.

  • To disable this email, set the sm_duo_seat_assignment_email feature flag to false. This flag is enabled by default.

After you assign seats, ensure GitLab Duo is set up for your GitLab Self-Managed instance.

Assign and remove GitLab Duo seats in bulk

You can assign or remove seats in bulk for multiple users.

SAML Group Sync

GitLab.com groups can use SAML Group Sync to manage GitLab Duo seat assignments.

For GitLab.com

  1. In the top bar, select Search or go to and find your group.
  2. Select Settings > GitLab Duo.
  3. On the bottom right, you can adjust the page display to show 50 or 100 items to increase the number of users available for selection.
  4. Select the users to assign or remove seats for:
    • To select multiple users, to the left of each user, select the checkbox.
    • To select all, select the checkbox at the top of the table.
  5. Assign or remove seats:
    • To assign seats, select Assign seat, then Assign seats to confirm.
    • To remove users from seats, select Remove seat, then Remove seats to confirm.

For GitLab Self-Managed

Prerequisites:

  • You must be an administrator.
  • You must have GitLab 17.5 or later.
  1. In the upper-right corner, select Admin.
  2. In the left sidebar, select GitLab Duo.
  3. On the bottom right, you can adjust the page display to show 50 or 100 items to increase the number of users available for selection.
  4. Select the users to assign or remove seats for:
    • To select multiple users, to the left of each user, select the checkbox.
    • To select all, select the checkbox at the top of the table.
  5. Assign or remove seats:
    • To assign seats, select Assign seat, then Assign seats to confirm.
    • To remove users from seats, select Remove seat, then Remove seats to confirm.
  6. To the right of the user, turn on the toggle to assign a GitLab Duo seat.

Administrators of GitLab Self-Managed instances can also use a Rake task to assign or remove seats in bulk.

Managing GitLab Duo seats with LDAP configuration

You can automatically assign and remove GitLab Duo seats for LDAP-enabled users based on LDAP group membership.

To enable this functionality, you must configure the duo_add_on_groups property in your LDAP settings.

When duo_add_on_groups is configured, it becomes the single source of truth for GitLab Duo seat management among LDAP-enabled users. For more information, see seat assignment workflow.

This automated process ensures that GitLab Duo seats are efficiently allocated based on your organization's LDAP group structure. For more information, see GitLab Duo add-on seat management with LDAP.

View assigned GitLab Duo users

{{< history >}}

  • Last GitLab Duo activity field introduced in GitLab 18.0.

{{< /history >}}

Prerequisites:

  • You must purchase a GitLab Duo Pro or Enterprise add-on, or have an active GitLab Duo trial.

After you purchase GitLab Duo Pro or Enterprise, you can assign seats to users to grant access to the add-on. Then you can view details of assigned GitLab Duo users.

The GitLab Duo seat utilization page shows the following information for each user:

  • User's full name and username
  • Seat assignment status
  • Public email address: The user's email displayed on their public profile.
  • Last GitLab activity: The date the user last performed any action in GitLab.
  • Last GitLab Duo activity: The date the user last used GitLab Duo features. Refreshes on any GitLab Duo activity.

These fields use data from the AddOnUser type in the GraphQL API.

For GitLab.com

Prerequisites:

  • You must have the Owner role.
  1. In the top bar, select Search or go to and find your group.
  2. Select Settings > GitLab Duo.
  3. By Seat utilization, select Assign seats.
  4. From the filter bar, select Assigned seat and Yes.
  5. User list is filtered to only users assigned a GitLab Duo seat.

For GitLab Self-Managed

Prerequisites:

  • You must be an administrator.
  • You must have GitLab 17.5 or later.
  1. In the upper-right corner, select Admin.
  2. In the left sidebar, select GitLab Duo.
    • If the GitLab Duo menu item is not available, synchronize your subscription after purchase:
      1. In the left sidebar, select Subscription.
      2. In Subscription details, to the right of Last sync, select synchronize subscription ({{< icon name="retry" >}}).
  3. By Seat utilization, select Assign seats.
  4. To filter by users assigned to a GitLab Duo seat, in the Filter users bar, select Assigned seat, then select Yes.
  5. User list is filtered to only users assigned a GitLab Duo seat.

Automatic seat removal

GitLab Duo add-on seats are removed automatically to ensure only eligible users have access. This happens when there are:

  • Seat overages
  • Blocked, banned, and deactivated users

At subscription expiration

If your subscription containing the GitLab Duo add-on expires, seat assignments are retained for 28 days. If the subscription is renewed, or a new subscription containing GitLab Duo is purchased during this 28-day window, users will be automatically re-assigned. Otherwise, seat assignments are removed and users must be reassigned.

For seat overages

If your quantity of purchased GitLab Duo add-on seats is reduced, seat assignments are automatically removed to match the seat quantity available in the subscription.

For example:

  • You have a 50 seat GitLab Duo Pro subscription with all seats assigned.
  • You renew the subscription for 30 seats. The 20 users over subscription are automatically removed from GitLab Duo Pro seat assignment.
  • If only 20 users were assigned a GitLab Duo Pro seat before renewal, then no removal of seats would occur.

Seats are selected for removal based on the following criteria, in this order:

  1. Users who have not yet used Code Suggestions, ordered by most recently assigned.
  2. Users who have used Code Suggestions, ordered by least recent usage of Code Suggestions.

For blocked, banned and deactivated users

Once or twice each day, a CronJob reviews GitLab Duo seat assignments. If a user who is assigned a GitLab Duo seat becomes blocked, banned, or deactivated, their access to GitLab Duo features is automatically removed.

After the seat has been removed, it becomes available and can be re-assigned to a new user.

Troubleshooting

Unable to use the UI to assign seats to your users

On the Usage quotas page, if you experience both of the following, you will be unable to use the UI to assign seats to your users:

  • The Seats tab does not load.

  • The following error message is displayed:

    plaintext
    An error occurred while loading billable members list.

As a workaround, you can use the GraphQL queries in this snippet to assign seats to users.