Keep your GitLab seats in check with restricted access

What this post added

This post details significant improvements to the 'Restricted Access' feature for seat control. Key enhancements include better integration with identity providers (SAML, SCIM, LDAP, OIDC) to assign Minimal Access roles instead of billable seats when no seats are available, preventing silent overages from dormant user reactivation by placing them in a pending approval state, and clearer in-product warnings, banners, and notifications for administrators. It also clarifies the difference between 'Restricted Access' and 'User Cap' and explains the self-managed settings cache behavior.