### Summary While using the [Group access tokens](https://docs.gitlab.com/ee/user/group/settings/group_access_tokens.html)feature on gitlab.com, the bots created are consuming the seats and users over license field is incrementing by 1 user for each project access token. This appears to only be an issue for gitlab.com. In self managed instances it appears that the users are not taking up a seat. ### Steps to reproduce * Log in to GitLab. * Navigate to the group you would like to create an access token for. * In the Settings menu choose Access Tokens. * Choose a name and optional expiry date for the token. * Choose the desired scopes. * Click the Create project access token button * Navigate to Billing * Navigate to "See Usage" * Note that "@group_XXXX_bot" users are showing up and counting against license seats | Before adding group access token | After adding group access token | | ------ | ------ | |  |  | ### What is the current *bug* behavior? Group access tokens are counting against license seats. ### What is the expected *correct* behavior? Group access tokens are not counted against license seats. #### Results of GitLab environment info _Gitlab.com_ ### Possible fixes _Unknown_ ### Related Items Related to #223695. Related to #214046.