Audit event for Minimal Access role assignment due to seat limits
What does this MR do and why?
Adds a new audit event (group_minimal_access_role_adjusted_seat_limit) that is recorded whenever a user is automatically assigned the Minimal Access (MA) role because no billable seats are available and Restricted Access (RA) is enabled.
References
- Users with Minimal Access
- Restricted Access:
- Audit events
Screenshots or screen recordings
| Instance | Audit Screenshot |
|---|---|
| GitLab.com | ![]() |
| Self-Manged | ![]() |
How to set up and validate locally
- Enable feature flag in Rails console
Feature.enable(:bso_minimal_access_fallback) - Enable Restricted Access (RA) on web - see documentation in references
- Trigger service call in Rails console
group = Group.last member = group.all_group_members.last include GitlabSubscriptions::MemberManagement::SeatAwareProvisioning audit_minimal_access_role_adjustment(group, member, Gitlab::Access::DEVELOPER) - See audit event at
- GitLab.com:
http://localhost:3000/groups/<group-path>/-/audit_events - Self-managed:
http://localhost:3000/admin/audit_logs
- GitLab.com:
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #580432
Edited by Sandra To

