Keep your GitLab seats in check with restricted access

This post details improvements to GitLab's restricted access feature for seat control. Key enhancements include better integration with identity providers (SAML, SCIM, LDAP, OIDC) to assign non-billable Minimal Access roles when seats are full, preventing immediate overages. Dormant users are now placed in a pending approval state upon reactivation if no seats are available, rather than being silently reactivated. The post also highlights clearer warnings, banners, and notifications for administrators regarding seat limits and user provisioning. It clarifies the difference between restricted access and user cap, and mentions the application settings cache on Self-Managed instances.