Skip to content

Group Access Tokens created in the top-level namespace are counted as licensed users

Summary

Group Access Tokens created in the top-level namespace are counted as licensed users when they should not be. This is confirmed by our documentation.

This was previously fixed via #350997 (closed) but appears to only have resolved the issue for subgroup access tokens.

Steps to reproduce

  • Log in to GitLab
  • Navigate to the top-level group
  • In the Settings menu choose Access Tokens
  • Choose a name and optional expiry date for the token
  • Choose the desired scopes
  • Click the Create group access token button
  • Navigate to Billing
  • Navigate to See Usage
  • Note that @group_XXXX_bot users are showing up and counting against license seats

What is the current bug behavior?

Bot users for groups (Group Access Tokens) count as licensed seats.

What is the expected correct behavior?

Bot users for groups (Group Access Tokens) should not count as licensed seats.

Relevant logs and/or screenshots

Screen_Shot_2022-02-14_at_2.58.17_PM

Screen_Shot_2022-02-14_at_3.01.04_PM

Output of checks

This bug happens on GitLab.com