I'm seeing a 403 Permission error!


This error most often occurs when clicking over to Code Climate from a GitHub pull request status update, or when trying to access a direct Code Climate link from an email or other outside sources.

But I should have access to that! Why am I seeing this error?

Below is a list of some of the most common reasons that can cause this error to occur and how to fix it:

  • Insufficient access to the GitHub repo: With GitHub-backed authorization, repo-level permissions are determined by a user's GitHub permissions. To view repo analysis on Code Climate, you'll need read access to the repo on GitHub. To view repo settings on Code Climate, you'll need admin access to the repo on GitHub. For more info, click here.

  • More than one Code Climate user: If you unknowingly have two Code Climate users, this can cause some confusion. In most cases where this is the issue, you're likely logged into a user that hasn't been added to the organization that owns the repository you're trying to access. In general, we recommend only maintaining one Code Climate user. The best course of action is to delete one of the users, and (if necessary) change the user that your GitHub user is linked to. To see which user you are logged in as, browse to the upper right hand corner of your Code Climate Dashboard, and click on your avatar.

  • Repository Permissions by Team: For Code Climate organizations created before January 2018 and not using GitHub-backed authorization, organization-level permissions in Code Climate are entirely separate from those in GitHub, or any other system. Whether or not a user can view a repository in our system is based entirely on which Code Climate team(s) they belong to. We recommend checking to see what Team you belong to in Code Climate, and check with an organization admin to see if this repository has been added to your Team for access. If the repository needs to be added to your team, please see our step by step instructions.

  • Repository Exists in Multiple Organizations: If the same repository is added to two different Organizations (perhaps a trial organization was set up twice by two different team members), your Code Climate user might not have access to the repo in the other existing Organization. If this is the case you are running into, we recommend deleting one of the trial organizations and inviting all of your team members to the remaining Code Climate organization.

Related Issues