Roles and permissions for organizations#
Your team members have different permission levels on Codacy depending on their role on your Git provider. To change the permission level of a user on Codacy, you must adjust their role directly on your Git provider so that Codacy will use the corresponding permission level on the next time that the user logs in to Codacy.
See the Codacy permission levels that correspond to each role on your Git provider:
See managing people to list and manage the members of your Codacy organization.
Permissions for GitHub#
The table below maps the GitHub Cloud and GitHub Enterprise roles to the corresponding Codacy permission levels and the operations that they're allowed to perform:
| GitHub role | Outside Collaborator1 |
Repository Read |
Repository Triage |
Repository Write |
Repository Maintain |
Repository Admin |
Organization Owner |
|---|---|---|---|---|---|---|---|
| Codacy permission level | - | Repository Read |
Repository Write |
Repository Admin |
Organization Admin |
||
| Join organization | No | Yes2 | Yes2 | Yes2 | Yes2 | ||
| View and follow private repository | No | Yes | Yes | Yes | Yes | ||
| Ignore issues and files, configure code patterns and file extensions, manage branches |
No | Configurable | Configurable | Yes | Yes | ||
| Upload coverage using an account API token, see the coverage report logs |
No | No | Yes | Yes | Yes | ||
| Configure repository | No | No | No | Yes | Yes | ||
| Add and remove repository | No | No | No | Yes | Yes | ||
| Manage coding standards, bulk copy patterns |
No | No | No | No | Yes | ||
| Configure default Git provider integration settings | No | No | No | No | Yes | ||
| Invite and accept members, modify billing |
No | No | No | No | Yes | ||
1: Outside Collaborators aren't supported as members of organizations on Codacy. You can still add Outside Collaborators to Codacy so that Codacy analyzes their commits to private repositories, but they won't be able to join your Codacy organization.
2: Joining an organization may need an approval depending on your setting for accepting new people.
Permissions for GitLab#
The table below maps the GitLab Cloud and GitLab Enterprise roles to the corresponding Codacy permission levels and the operations that they're allowed to perform:
| GitLab role | External User1 |
Project Guest |
Project Reporter |
Project Developer |
Project Maintainer |
Project Owner |
Group Owner |
Administrator |
|---|---|---|---|---|---|---|---|---|
| Codacy permission level | - | Repository Read |
Repository Write |
Repository Admin |
Organization Admin |
|||
| Join organization | No | Yes2 | Yes2 | Yes2 | Yes2 | |||
| View and follow private repository | No | Yes | Yes | Yes | Yes | |||
| Ignore issues and files, configure code patterns and file extensions, manage branches |
No | Configurable | Configurable | Yes | Yes | |||
| Upload coverage using an account API token, see the coverage report logs |
No | No | Yes | Yes | Yes | |||
| Configure repository | No | No | No | Yes | Yes | |||
| Add and remove repository | No | No | No | Yes | Yes | |||
| Manage coding standards, bulk copy patterns |
No | No | No | No | Yes | |||
| Configure default settings for Git provider integration | No | No | No | No | Yes | |||
| Invite and accept members, modify billing |
No | No | No | No | Yes | |||
1: External Users aren't supported as members of organizations on Codacy. You can still add External Users to Codacy so that Codacy analyzes their commits to private repositories, but they won't be able to join your Codacy organization.
2: Joining an organization may need an approval depending on your setting for accepting new people.
Permissions for Bitbucket#
The table below maps the Bitbucket Cloud and Bitbucket Server roles to the corresponding Codacy permission levels and the operations that they're allowed to perform:
| Bitbucket role | Read | Write1 | Admin |
|---|---|---|---|
| Codacy permission level | Repository Read |
Organization Admin |
|
| Join organization | Yes2 | Yes2 | |
| View and follow private repository | Yes | Yes | |
| Ignore issues and files, configure code patterns and file extensions, manage branches |
Configurable | Yes | |
| Upload coverage using an account API token, see the coverage report logs |
No | Yes | |
| Configure repository | No | Yes | |
| Add and remove repository | No | Yes | |
| Manage coding standards, bulk copy patterns |
No | Yes | |
| Configure default settings for Git provider integration | No | Yes | |
| Invite and accept members, modify billing |
No | Yes | |
1: Codacy can't distinguish the Bitbucket roles Read and Write because of a limitation on the Bitbucket API.
2: Joining an organization may need an approval depending on your setting for accepting new people.
Configuring who can change the analysis configuration#
By default, only users with the Codacy permission level Repository Write can change analysis configurations.
To change this, open your organization Settings, page Member privileges, and define the lowest Codacy permission level required to perform the following operations on the repositories of your organization:
Note
Codacy determines the permission level of each user from the role that each user has on your Git provider:
See also#
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.
Edit this page on GitHub if you notice something wrong or missing.
If you have a question or need help please contact support@codacy.com.