Administrative permissions¶

Organization permissions allow fine-grained control over your organization's members and repositories.

All organizations have an Administrators team. Each member of this team is an administrator of the entire organization, and all repositories in the organization are automatically added to this team.

Any member of the Administrators team has full read/write permissions. You can view the actions available per permission level here:

Organization
Admin	Add/Remove members Create/Remove teams Change organization settings Edit Billing information Delete Organization Add/Remove repositories Add/Remove integrations of team repositories Change code patterns Define/Change quality settings See repository issues and metrics

For users that don't have Admin permissions, they will need to be added to a team. When adding users to a team, the Administrator can decide the level of permissions each team member should have for the repositories within that team.

Team
Read	See repository issues and metrics Add repositories to the Administrators team (to add repo to a specific team needs to have write permissions)
Write	Same as Read permissions plus: Add repositories to specific teams Add/Remove integrations of team repositories Change code patterns See repository issues and metrics Ignore issues / remove patterns

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.

If you have a question or need help please contact support@codacy.com.

Last modified August 7, 2020