[JENKINS-59624] Disable Scan Organization for users that are not authorized to do so - GitHub Branch Source

Hi,

The GitHub Branch Source plugin implements the feature of `Scan Organization`, which basically scans a whole organization for GitHub repositories and updates them in Jenkins.

 

This is useful but usually we hit the API rate limit. I know that are are issues to handle this. However, the fact that everyone is able to click on `Scan Organization Now`, is a problem because usually only the Jenkins admins are aware of this. In big organizations, with hundreds of people using Jenkins (as users, not admins) this impacts.

 

Current behaviour

Everyone is able to click on `Scan Organization Now`.

 

Proposed behaviour

Only admins or people with specific role should be able to activate that feature.

There are a couple of implementations:

• Only admins should be able to trigger that feature


• Only users with Configure permission should be able to trigger that feature


• We could create a new permission type and only users with that permission type should be able to trigger that feature

 

---
Originally reported by atcarmo, imported from: Disable Scan Organization for users that are not authorized to do so - GitHub Branch Source

• status: Open
  
• priority: Minor
  
• component(s): github-branch-source-plugin
  
• resolution: Unresolved
  
• votes: 1
  
• watchers: 1
  
• imported: 2025-12-02
  

Raw content of original issue

Hi,


The GitHub Branch Source plugin implements the feature of `Scan Organization`, which basically scans a whole organization for GitHub repositories and updates them in Jenkins.


 


This is useful but usually we hit the API rate limit. I know that are are issues to handle this. However, the fact that everyone is able to click on `Scan Organization Now`, is a problem because usually only the Jenkins admins are aware of this. In big organizations, with hundreds of people using Jenkins (as users, not admins) this impacts.


 


Current behaviour


Everyone is able to click on `Scan Organization Now`.


 


Proposed behaviour


Only admins or people with specific role should be able to activate that feature.


There are a couple of implementations:



	
Only admins should be able to trigger that feature

	
Only users with Configure permission should be able to trigger that feature

	
We could create a new permission type and only users with that permission type should be able to trigger that feature



 

• environment: 2.5.3