Answers: <p>This ended up being a usability bug and GitLab has made a change to avoid future confusion on this point. The relevant ticket for this is here: <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/337041" rel="nofollow noreferrer">https://gitlab.com/gitlab-org/gitlab/-/issues/337041</a></p>
  
Answers: CC BY-SA 4.0
Answers: 2021-08-27T19:21:25.777Z
Answers: 2021-08-27T19:21:25.777Z
Answers: James T Snell
Body: <p>I'm running the latest version of on-prem GitLab (version 14.1.0-ee). The last few new GitLab runners I've added show up as locked. I open the runners config in the WebUI and I see that the &quot;Lock to current projects&quot; checkbox for locking them is disabled, but also checked-on, like this:<BR>
  <a href="https://i.sstatic.net/SI6uD.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/SI6uD.png" alt="Lock to current projects" /></a></p>
  <p>How do I enable (unlock) these runners?</p>
  <p>I see if I assign them to a specific project, then they'll unlock. But if I then remove them from those projects, they lock again.</p>
  
Comments: CC BY-SA 4.0
Comments: 2021-08-26T17:23:34.180Z
Comments: When you registered the runner(s), did you use a specific project's registration token, or the Gitlab Instance's registration token (assuming you're running your own GitLab instance and not using Gitlab.com)?
Comments: Adam Marshall
Comments: CC BY-SA 4.0
Comments: 2021-08-26T22:40:48.353Z
Comments: @AdamMarshall - I used an instance-wide token and yes, I'm using an on-prem instance. I eventually reported this as a bug/improvement thing to GitLab and they quickly implemented a resolution, the ticket for that is here: https://gitlab.com/gitlab-org/gitlab/-/issues/337041
Comments: James T Snell
Comments: CC BY-SA 4.0
Comments: 2021-08-27T04:11:49.687Z
Comments: Awesome, glad you resolved it!
Comments: Adam Marshall
Tags: <gitlab><gitlab-ci-runner>
Title: New Runners are locked and the checkbox to unlock them is disabled
UserDisplayName: James T Snell
ThreadText: # New Runners are locked and the checkbox to unlock them is disabled
  
  (Asked by: username_0 on 2021-07-27)
  
  I'm running the latest version of on-prem GitLab (version 14.1.0-ee). The last few new GitLab runners I've added show up as locked. I open the runners config in the WebUI and I see that the "Lock to current projects" checkbox for locking them is disabled, but also checked-on, like this:  
  [![Lock to current projects](https://i.sstatic.net/SI6uD.png)](https://i.sstatic.net/SI6uD.png)
  
  How do I enable (unlock) these runners?
  
  I see if I assign them to a specific project, then they'll unlock. But if I then remove them from those projects, they lock again.
  
  **Tags:** gitlab, gitlab-ci-runner
  
  > **Comments:**
  > **username_1**: When you registered the runner(s), did you use a specific project's registration token, or the Gitlab Instance's registration token (assuming you're running your own GitLab instance and not using Gitlab.com)?  
  > **username_0**: @username_1 - I used an instance-wide token and yes, I'm using an on-prem instance. I eventually reported this as a bug/improvement thing to GitLab and they quickly implemented a resolution, the ticket for that is here: https://gitlab.com/gitlab-org/gitlab/-/issues/337041  
  > **username_1**: Awesome, glad you resolved it!  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2021-08-27. Score: 2 | Accepted answer
  
  This ended up being a usability bug and GitLab has made a change to avoid future confusion on this point. The relevant ticket for this is here: <https://gitlab.com/gitlab-org/gitlab/-/issues/337041>
  
  
  ---
  
  