Overview
If you are seeing permission errors in CircleCI but your user has the correct permissions in GitHub or BitBucket (including unauthorized or blocked builds, organization is not listed, ...etc), you can first try refreshing permissions. If this does not solve the issue, we recommend performing a full re-authentication. This will force CircleCI to re-sync permissions from your VCS.
Depending on the VCS you're using (GitHub or Bitbucket), you can perform this operation as outlined below.
GitHub users
NOTE: Taking the steps below will clear any user keys that have been generated for any of your projects.
Sign out of your CircleCI account
Revoke CircleCI's access in GitHub > https://github.com/settings/applications
Clear your browser's cache and cookies
Sign back into your CircleCI account
Make sure that all organizations, especially those needing SSO access are granted access, like so:
Bitbucket users
NOTE: Taking the steps below will clear any user keys that have been generated for any of your projects.
Sign out of your CircleCI account
Revoke CircleCI's access in Bitbucket > https://bitbucket.org/account/settings/app-authorizations/
Clear your browser's cache and cookies
Sign back into your CircleCI account
Grant access/authorize your BitBucket account
Additional resources
CircleCI Documentation: Permissions overview for GitHub OAuth Integration
CircleCI Documentation: Permissions overview for BitBucket Integration