Discussion: Exceptions for who counts as a billable member (SM)
Summary
Currently, every occupied seat, whether by person, administrator, job or bot is counted in the subscription on a self-managed instance, with the following exceptions:
- Blocked users who are blocked prior to the renewal of a subscription will not be counted as Active Users for the renewal subscription but may count as true-up users for the term in which they were originally added.
- Members with Guest permissions on an Ultimate subscription do not count towards the subscription.
- Ghost User, Support Bot, Migration Bot, and Alert Bot do not count towards the subscription.
Customers may feel that the following scenarios should exclude a user from taking up a seat as a billable member:
- The user has never logged in
- The user has logged in, but there has been no activity on their account
- The user has never logged in/used Gitlab, but they are using GitLab OAuth for an app like Mattermost
- The user was added by accident (for example: via an import or if sign-up restriction was not enabled)
Discussion
Are any of the scenarios above eligible to be re-evaluated so that these users do not take up a license seat?