Fulfillment: Seat Management direction

Last updated: 2025-08

Mission

Enable customers to optimize their GitLab investment through intuitive seat assignment, proactive cost management, and seamless enterprise user provisioning.

Overview

The Seat Management group is responsible for the Seat Cost Management and User Management product categories, providing customers with comprehensive tools and features needed to efficiently manage user access, control seat costs, and integrate GitLab with existing enterprise identity systems.

By focusing on these areas, the Seat Management group aims to eliminate billing surprises, reduce administrative overhead for user management, and enable organizations to scale their GitLab usage efficiently while maintaining security and cost control.

Vision

What is our long-term solution concept? Analogy: what will it look like at the top of the mountain?

Today, seat assignment, management, user provisioning, and enterprise user controls present opportunities for improvement. Examples of how customers are impacted by these challenges:

• Customers currently manage seat assignment manually for add-ons like Duo Pro and Duo Enterprise, and base plans (Premium/Ultimate) derive seats from user roles rather than explicit assignment, leading to less predictable resource allocation.
• Organizations lack comprehensive visibility into seat usage and proactive controls to prevent unexpected overages during budget planning.
• While enterprise user management through SCIM, SAML, and LDAP works well, there are opportunities to better integrate these capabilities with cost control features like Restricted Access (Block Seat Overages) to enable broader adoption.
• Current role-based seat consumption can create unexpected billing scenarios when users transition between roles.

To solve these problems we are going to:

1. Develop a seat assignment model (SAM). We’ll move away from users immediately consuming a subscription seat when being added to a group or project based on their role. With SAM, group owners and admins assign users to seat types first, and these seat types then control what roles users can have in groups and projects. This will move us away from users being able to unintentionally transition between roles, which can have billable and compliance consequences.
2. Prevent unintended overages. Today, all customers are charged for seat overages. In the future, the default experience will require customers to purchase seats before they can be assigned to users.
3. Enhance enterprise user management integration with cost controls. We’ll improve how SCIM provisioning, SAML Group Sync, and LDAP synchronization work with Restricted Access (Block Seat Overages), enabling more customers to adopt these cost control features while maintaining seamless user lifecycle management.

These changes will not be universally felt by customers:

• For some customers that are optimizing for frictionless addition of new users, they will be able to continue to interact with GitLab as they do today while also appreciating enhancements like a consolidated users view in GitLab.com and optimized billable calculations. If they want more controls for cost, they can opt-in to those.
• However, for most customers who are optimizing for cost control, we will be providing them with additional controls and visibility for cost management.

1-year Roadmap

Where are we focused over the next 12 months to make meaningful steps towards achieving our vision and increasing feature maturity?

Further Details (Not Public)

Seat Management FY26 Roadmap.

Possible Future Opportunities

All Seat Management group epics and issues are organized in the group’s HQ epic.

Target audiences

The Seat Management group serves:

• Self-managed, GitLab.com and GitLab Dedicated self-service customers
• Self-managed, GitLab.com and GitLab Dedicated sales-assisted customers
• Self-managed, GitLab.com and GitLab Dedicated channel partners and their customers

Our customers fit the buyer persona and may play a different role in the decision-making and purchasing process depending on their company size and their role.

• For SMB and mid-market companies: The application development manager needs to have visibility into usage across their teams and be able to control usage in a way that fits their company preferences/processes/budget.
• For large or enterprise companies: The release and change management director is concerned with accurate billing and being able to make purchasing decisions based on usage information.

Internal teams we serve:

• Support
• Customer Success
• Sales

Feature Overview and Maturity

What features are the Seat Management group responsible for and how mature are they?

Legend:

• 🌱 Planned: Not yet implemented, but on our roadmap.
• 🙂 Minimal: Available and works for a small number of use cases. Some transparency for internal teams.
• 😊 Viable: Available and works for majority of use cases. Some transparency for internal teams.
• 😁 Complete: Fully functional for all eligible use cases. Full transparency for internal teams.
• 😍 Lovable: Glowing review from external and internal users.

View page source - Edit this page - please contribute.