[[_TOC_]] ## Problem Currently, a Guest user can move _themselves_ into a paid seat by creating a project in their personal namespace and adding themselves to a role higher than Guest on that project. This means that admins have less visibility and control over whether or not a user takes up a paid seat. https://docs.gitlab.com/ee/user/permissions.html#free-guest-users-ultimate ## Designs https://gitlab.com/gitlab-org/gitlab/-/issues/419645+ ## Solutions **Recommendation**: **Recommendation**: [Iteration 1](https://gitlab.com/gitlab-org/gitlab/-/issues/415616 "[SM - Iteration 1] Don't allow Guest users to move themselves into a paid seat") + ~~Iteration 2 -- Option A (or B pending outcome of ~~[~~data~~](https://gitlab.com/gitlab-data/product-analytics/-/issues/1383 "Fulfillment - Utilization: Rate of SM Guests Creating Personal Projects")~~) but open to all pathways:~~ Iteration 2 -- Option D, per discussion [here](https://docs.google.com/document/d/1ZT6a-jPZ-D1VBIJ_o-mKiNk39bNLVzHLV_s4QZxv69M/edit?usp=sharing) <table> <tr> <th>Iteration</th> <th>Solution</th> <th>Link</th> <th>Where we are</th> </tr> <tr> <td>1</td> <td> Tell this audience to make these guests [external](https://docs.gitlab.com/ee/administration/external_users.html) </td> <td> https://gitlab.com/gitlab-org/gitlab/-/issues/415616 https://gitlab.com/gitlab-org/gitlab/-/issues/426298 </td> <td> :white_check_mark: </td> </tr> <tr> <td>2 - Option D</td> <td>Add a new global setting which can be disabled by Admin to "allow guest users from creating Personal projects". This will impact All Guest users.</td> <td> https://gitlab.com/gitlab-org/gitlab/-/issues/426279 </td> <td> :white_check_mark: </td> </tr> </table> ## Additional Notes ### Related Issues Created During Solution Validation _During the course of solution validation, we found other related problems that should likely get fixed but aren't part of the original problem. We won't aim to fix these as part of the solution._ * https://gitlab.com/gitlab-org/gitlab/-/issues/426160+ * https://gitlab.com/gitlab-org/gitlab/-/issues/426388+ * https://gitlab.com/gitlab-org/gitlab/-/issues/432782+ ### Documentation A lot of discussion around this epic is from this issue https://gitlab.com/gitlab-org/gitlab/-/issues/415616 Prior epic link: https://gitlab.com/groups/gitlab-org/-/epics/7170 <details> <summary>Initial Proposals</summary> Guest users should either: 1. Not be able to create personal projects 2. Only have access to Free features on their personal projects </details> <details> <summary>Proposal Gap</summary> From `@timnoah` -- Are there any intentions to handle customers who have Guests currently taking up a seat via a personal project? Just thinking of potential ways to help mitigate this unwanted scenario for Admins. Could one way be to give Admins the ability to bulk convert personal projects of Guests into a readonly state and remove them as owner </details>