# Github organization private repo & Github scope question

**URL:** <https://drone.discourse.group/t/github-organization-private-repo-github-scope-question/7659>\
**Category:** Drone Support\
**Created:** [January 9, 2018, 8:45am UTC](https://drone.discourse.group/t/github-organization-private-repo-github-scope-question/7659 "2018-01-09T08:45:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![JulienTant](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/julientant/32/4043_2.png) [@JulienTant](https://drone.discourse.group/u/JulienTant)\
**Post date:** [January 9, 2018, 8:45am UTC](https://drone.discourse.group/t/github-organization-private-repo-github-scope-question/7659/1 "2018-01-09T08:45:27Z")

</div>

Hello,

First a bit of context :

I just joined a company (as a Freelancer) which is setting up drone ATM. They have a Github Organization with private repositories. They invited me to join drone, but i noticed that drone wants access to my private repositories. This is complex situation because i have code source of other clients projects in my privates repository.

So my question is, will anyone have access to my private repository list if I accept to join the OAuth application ? And what’s the best way to handle that problem ?

Thanks a lot for your time !

---

<div class="post-metadata">

**Author:** ![nodefortytwo](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/nodefortytwo/32/4791_2.png) [@nodefortytwo](https://drone.discourse.group/u/nodefortytwo)\
**Post date:** [September 25, 2018, 12:47pm UTC](https://drone.discourse.group/t/github-organization-private-repo-github-scope-question/7659/2 "2018-09-25T12:47:03Z")

</div>

This is quite a common problem with github generally (its IAM sucks) a lot of our devs create a new github account with the name of the company they are working for.

ie, nodefortytwo-dazn

Keeps everything isolated and easy to delete after your contract ends.

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [September 25, 2018, 3:24pm UTC](https://drone.discourse.group/t/github-organization-private-repo-github-scope-question/7659/3 "2018-09-25T15:24:44Z")

</div>

there is also a feature built-in to Drone Enterprise that helps limit repositories:  
[http://docs.drone.io/custom-access-policies/](http://docs.drone.io/custom-access-policies/)

---

<div class="post-metadata">

**Author:** ![robertstettner](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/robertstettner/32/3803_2.png) [@robertstettner](https://drone.discourse.group/u/robertstettner)\
**Post date:** [September 25, 2018, 3:53pm UTC](https://drone.discourse.group/t/github-organization-private-repo-github-scope-question/7659/4 "2018-09-25T15:53:54Z")

</div>

You could just create an AWS Lambda using a scheduled CloudWatch event that has access to the Drone Database to purge unwanted repos.