Roles and permissions for synced organizations#
Depending on your role on the Git provider you will have different permissions on Codacy:
|Provider||Role||Join organization||View private repository||Ignore issues and files,
configure code patterns and file extensions,
|Configure repository||Add repository||Manage coding standards,
Bulk copy patterns
|Invite and accept members,
|GitHub Cloud and GitHub Enterprise||Outside Collaborator1||No||No||No||No||No||No||No|
|GitLab Cloud and GitLab Enterprise||External User1||No||No||No||No||No||No||No|
|Bitbucket Cloud and Bitbucket Server||Read, Write3||Yes2||Yes||Configurable||No||No||No||No|
1: Outside Collaborators and External Users aren't supported as Members of organizations on Codacy. However, you can add them so that Codacy analyzes their commits to private repositories.
2: Joining an organization may need an approval depending on your setting for accepting new people.
3: Codacy can't distinguish the Bitbucket roles Read and Write because of a limitation on the Bitbucket API.
See managing people to list and manage the members of your organization.
Configuring who can change analysis configurations#
By default, only users with Write permission on a repository can change analysis configurations.
To change this, open your organization Settings, page Member privileges, and define the lowest permission required to perform the following operations on the repositories of your organization:
Codacy doesn't allow changing the role of a user, as the roles on Codacy are mirrored from your Git provider and applied to each repository.
Share your feedback 📢
Did this page help you?
Thanks for the feedback! Is there anything else you'd like to tell us about this page?
255 characters left
We're sorry to hear that. Please let us know what we can improve:
255 characters left
Alternatively, you can create a more detailed issue on our GitHub repository.
Thanks for helping improve the Codacy documentation.