In order to keep your code secure, GitHub organizations are often set to require that third-party applications, like RBCommons, have their access explicitly granted by an organization administrator. This is the case by default with newer organizations, and many older ones have this on as well.

If you've tried to link one of your GitHub organization's repositories to RBCommons, you may have received an error message stating that the repository could not be found. This may simply mean that RBCommons doesn't yet have the permission to access it.

In this guide, we'll help you grant that access.

Step 1: Verify your organization's third-party access settings

Have an organization admin navigate to your organization page ( using their admin account. Click Settings, and then click Third-party access on the left.

From here, you'll be able to see the current access policy and any approved applications.

If Policy says Access restricted, then continue on with this guide.

However, if it says No restrictions, then you don't need to worry about this guide, and should double-check the information you entered into the repository form instead (if it gave you an error about not being able to find your repository).

Keep this page handy. You'll need to come back to it.

Step 2: Request or grant access for RBCommons

Make sure you're logged in as the user whose account was linked to Review Board when configuring the repository. Go to your settings page (click your avatar in the top-right of any page on GitHub, and then click Settings). Then click Applications on the left.

RBCommons should appear in this list under Authorized Applications. Click on RBCommons.

From here, you'll see a list of organizations you belong to that have access to your application, and any that need access to be granted. Your organization should appear in this list along with a button for requesting or granting access.

If you're an organization admin...

Click Grant access from here. You're done! Go back and save your repository again, and you should be all set up.

If you're not an organization admin...

Click Request access and follow the instructions. You'll then need to continue with step 3.

Step 3: Approve requested access to RBCommons

If you clicked Request access above, you'll now need an organization admin to approve it (by clicking Grant Access above). The administrator from Step 1 should reload the page they were on in that step. RBCommons should now be in the list. Simply approve the application from there, and you should be good to go.

Then, simply save the repository again in RBCommons. You're done!