From 6a77c8576eca014079bf30d22569818e9d27d1db Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Wed, 12 Aug 2026 14:16:43 +0100 Subject: [PATCH 1/5] docs: reorganize roles and permissions by Codacy role Splits the three wide GitHub/GitLab/Bitbucket permission grids (up to 10 columns each) into short per-provider role-mapping lists plus one shared set of narrow Operation|Allowed tables per Codacy role. The same permission values were being repeated identically across all three provider tables; this states each fact once instead of three times and removes the horizontal scroll. Follow-up to #2731, which did the analogous reorg for supported-languages-and-tools.md. Co-Authored-By: Claude Sonnet 5 --- ...roles-and-permissions-for-organizations.md | 614 +++++------------- 1 file changed, 158 insertions(+), 456 deletions(-) diff --git a/docs/organizations/roles-and-permissions-for-organizations.md b/docs/organizations/roles-and-permissions-for-organizations.md index 73d6736cca..fa5f64d9fc 100644 --- a/docs/organizations/roles-and-permissions-for-organizations.md +++ b/docs/organizations/roles-and-permissions-for-organizations.md @@ -13,12 +13,14 @@ Organization admins can also grant additional permissions: - To roles, by [configuring repository management permissions](#change-analysis-configuration) - To individual members, by [assigning the organization manager role](#managing-the-organization-manager-role) -To review the permissions granted by each role, see the tables for each Git provider: +To find your Codacy role, see the roles for your Git provider: - [Permissions for GitHub](#permissions-for-github) - [Permissions for GitLab](#permissions-for-gitlab) - [Permissions for Bitbucket](#permissions-for-bitbucket) +Then see what that role can do in [Permissions by Codacy role](#permissions-by-codacy-role). + To list and manage the members of your Codacy organization, see the [Managing people](managing-people.md) page. ## Configuring repository management permissions {: id="change-analysis-configuration"} @@ -42,7 +44,7 @@ To change this, open your organization **Settings**, page **Roles and permission To grant an organization member additional permissions, you can assign that member the organization manager role. This role isn't influenced by a member's Git provider role. -To review the additional permissions granted by the organization manager role, see the tables for each Git provider ([GitHub](#permissions-for-github), [GitLab](#permissions-for-gitlab), [Bitbucket](#permissions-for-bitbucket)). +To review the additional permissions granted by the organization manager role, see [Organization manager](#organization-manager). !!! note Organization managers can access the **Policies** and **Integrations** settings sections of your organization and can therefore impact some repository settings for all repositories of your organization, even repositories that they can't access on the Git provider. However, they can't access the repositories themselves and can only see the repository names. @@ -72,489 +74,194 @@ To revoke the organization manager role: ## Permissions for GitHub -The table below maps the GitHub Cloud and GitHub Enterprise roles to the corresponding Codacy roles and the operations that they're allowed to perform: +The following GitHub Cloud and GitHub Enterprise roles map to these Codacy roles: + +- **Outside collaborator1:** not supported as a Codacy role +- **Repository read, Repository triage:** [Repository read](#repository-read) +- **Repository write, Repository maintain:** [Repository write](#repository-write) +- **Repository admin:** [Repository admin](#repository-admin) +- **No GitHub role maps here—assigned directly on Codacy:** [Organization manager](#organization-manager) +- **Organization Owner:** [Organization admin](#organization-admin) + +1: Outside collaborators aren't supported as members of organizations on Codacy. You can still [add outside collaborators to Codacy](managing-people.md#adding-people) so that Codacy analyzes their commits to private repositories, but they won't be able to join your Codacy organization. + +## Permissions for GitLab + +The following GitLab Cloud and GitLab Enterprise roles map to these Codacy roles: + +- **External user1:** not supported as a Codacy role +- **Project guest, Project reporter:** [Repository read](#repository-read) +- **Project developer:** [Repository write](#repository-write) +- **Project maintainer, Project owner:** [Repository admin](#repository-admin) +- **No GitLab role maps here—assigned directly on Codacy:** [Organization manager](#organization-manager) +- **Group owner, Administrator:** [Organization admin](#organization-admin) + +1: External users aren't supported as members of organizations on Codacy. You can still [add external users to Codacy](managing-people.md#adding-people) so that Codacy analyzes their commits to private repositories, but they won't be able to join your Codacy organization. + +## Permissions for Bitbucket + +The following Bitbucket Cloud and Bitbucket Server roles map to these Codacy roles: + +- **Read, Write1:** [Repository read](#repository-read) +- **No Bitbucket role maps here—assigned directly on Codacy:** [Organization manager](#organization-manager) +- **Admin:** [Organization admin](#organization-admin) + +Bitbucket has no role that maps to [Repository write](#repository-write) or [Repository admin](#repository-admin). + +1: Codacy can't distinguish the Bitbucket roles Read and Write because of a limitation on the Bitbucket API. + +## Permissions by Codacy role + +The tables below list what each Codacy role is allowed to do. These permissions are the same regardless of Git provider—see [Permissions for GitHub](#permissions-for-github), [Permissions for GitLab](#permissions-for-gitlab), or [Permissions for Bitbucket](#permissions-for-bitbucket) to find your Codacy role. + +### Repository read - - - - - - - - - + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + +
GitHub roleOutside
collaborator1
Repository
read
Repository
triage
Repository
write
Repository
maintain
Repository
admin
-Organization
Owner
OperationAllowed
Codacy role-Repository
read
Repository
write
Repository
admin
Organization
manager
Organization
admin
Join organizationNoYes2Yes2Yes2YesYes2
View and follow private repositoryNoYesYesYesYesYes
Access Security and risk managementNoYes3Yes3Yes3YesYes
Access AI Risk Hub OverviewNoYesYesYesYesYes
Access AI Risk Hub AI assets and Tools & workflowsNoNoNoNoYesYes
Ignore issues and files,
configure code patterns,
reanalyze branches and pull requests
NoConfigurableConfigurableYesInherits original permissionYes
Upload coverage using an account API token,
see the coverage report logs
NoNoYesYesInherits original permissionYes
Configure repository Git provider integration settingsNoNoNoYesInherits original permissionYes
Configure repository quality gates and goalsNoNoNoYesInherits original permissionYes
Enable repository analysis to run on a local build server, manage repository API tokensNoNoNoYesInherits original permissionYes
Add and remove repositoryNoNoNoYes4Inherits original permissionYes
Manage organization gate policies and coding standardsNoNoNoNoYesYes
Configure organization default settings for Git provider integrationNoNoNoNoYesYes
Obtain audit logs for organization events5NoNoNoNoYesYes
Invite and accept members,
modify billing
NoNoNoNoNoYes
Assign and revoke the organization manager roleNoNoNoNoNoYes
Join organizationYes1
View and follow private repositoryYes
Access Security and risk managementYes2
Access AI Risk Hub OverviewYes
Access AI Risk Hub AI assets and Tools & workflowsNo
Ignore issues and files, configure code patterns, reanalyze branches and pull requestsConfigurable
Upload coverage using an account API token, see the coverage report logsNo
Configure repository Git provider integration settingsNo
Configure repository quality gates and goalsNo
Configure repository to run analysis on a local build server, manage repository API tokensNo
Add and remove repositoryNo
Manage organization gate policies and coding standardsNo
Configure organization default settings for Git provider integrationNo
Obtain audit logs for organization events4No
Invite and accept members, modify billingNo
Assign and revoke the organization manager roleNo
-1: Outside collaborators aren't supported as members of organizations on Codacy. You can still [add outside collaborators to Codacy](managing-people.md#adding-people) 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](changing-your-plan-and-billing.md#allowing-new-people-to-join-your-organization). -3: These users can only see security items originating from Codacy repositories that they follow. -4: Requires that an organization owner has given the Codacy GitHub App access to the repositories to add or remove. -5: [Audit logs](./audit-logs-for-organizations.md) are available only on [Business plan](https://www.codacy.com/pricing). - -## Permissions for GitLab - -The table below maps the GitLab Cloud and GitLab Enterprise roles to the corresponding Codacy roles and the operations that they're allowed to perform: +### Repository write - - - - - - - - - - + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + +
GitLab roleExternal
user1
Project
guest
Project
reporter
Project
developer
Project
maintainer
Project
owner
-Group
owner
AdministratorOperationAllowed
Codacy role-Repository
read
Repository
write
Repository
admin
Organization
manager
Organization
admin
Join organizationNoYes2Yes2Yes2YesYes2
View and follow private repositoryNoYesYesYesYesYes
Access Security and risk managementNoYes3Yes3Yes3YesYes
Access AI Risk Hub OverviewNoYesYesYesYesYes
Access AI Risk Hub AI assets and Tools & workflowsNoNoNoNoYesYes
Ignore issues and files,
configure code patterns,
reanalyze branches and pull requests
NoConfigurableConfigurableYesInherits original permissionYes
Upload coverage using an account API token,
see the coverage report logs
NoNoYesYesInherits original permissionYes
Configure repository Git provider integration settingsNoNoNoYesInherits original permissionYes
Configure repository quality gates and goalsNoNoNoYesInherits original permissionYes
Configure repository to run analysis on local build server, manage repository API tokensNoNoNoYesInherits original permissionYes
Add and remove repositoryNoNoNoYesInherits original permissionYes
Manage organization gate policies and coding standardsNoNoNoNoYesYes
Configure organization default settings for Git provider integrationNoNoNoNoYesYes
Obtain audit logs for organization events4NoNoNoNoYesYes
Invite and accept members,
modify billing
NoNoNoNoNoYes
Assign and revoke the organization manager roleNoNoNoNoNoYes
Join organizationYes1
View and follow private repositoryYes
Access Security and risk managementYes2
Access AI Risk Hub OverviewYes
Access AI Risk Hub AI assets and Tools & workflowsNo
Ignore issues and files, configure code patterns, reanalyze branches and pull requestsConfigurable
Upload coverage using an account API token, see the coverage report logsYes
Configure repository Git provider integration settingsNo
Configure repository quality gates and goalsNo
Configure repository to run analysis on a local build server, manage repository API tokensNo
Add and remove repositoryNo
Manage organization gate policies and coding standardsNo
Configure organization default settings for Git provider integrationNo
Obtain audit logs for organization events4No
Invite and accept members, modify billingNo
Assign and revoke the organization manager roleNo
-1: External users aren't supported as members of organizations on Codacy. You can still [add external users to Codacy](managing-people.md#adding-people) 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](changing-your-plan-and-billing.md#allowing-new-people-to-join-your-organization). -3: These users can only see security items originating from Codacy repositories that they follow. -4: [Audit logs](./audit-logs-for-organizations.md) are available only on [Business plan](https://www.codacy.com/pricing). - -## Permissions for Bitbucket - -The table below maps the Bitbucket Cloud and Bitbucket Server roles to the corresponding Codacy roles and the operations that they're allowed to perform: +### Repository admin - - - - - + + + + + + + + + + + + + + + + + + + +
Bitbucket roleReadWrite1-AdminOperationAllowed
Join organizationYes1
View and follow private repositoryYes
Access Security and risk managementYes2
Access AI Risk Hub OverviewYes
Access AI Risk Hub AI assets and Tools & workflowsNo
Ignore issues and files, configure code patterns, reanalyze branches and pull requestsYes
Upload coverage using an account API token, see the coverage report logsYes
Configure repository Git provider integration settingsYes
Configure repository quality gates and goalsYes
Configure repository to run analysis on a local build server, manage repository API tokensYes
Add and remove repositoryYes3
Manage organization gate policies and coding standardsNo
Configure organization default settings for Git provider integrationNo
Obtain audit logs for organization events4No
Invite and accept members, modify billingNo
Assign and revoke the organization manager roleNo
+ +### Organization manager + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + +
Codacy roleRepository
read
Organization
manager
Organization
admin
Join organizationYes2YesYes2
View and follow private repositoryYesYesYes
Access Security and risk managementYes3YesYes
Access AI Risk Hub OverviewYesYesYes
Access AI Risk Hub AI assets and Tools & workflowsNoYesYes
Ignore issues and files,
configure code patterns,
reanalyze branches and pull requests
ConfigurableInherits original permissionYes
Upload coverage using an account API token,
see the coverage report logs
NoInherits original permissionYes
Configure repository Git provider integration settingsNoInherits original permissionYes
Configure repository quality gates and goalsNoInherits original permissionYes
Configure repository to run analysis on local build server, manage repository API tokensNoInherits original permissionYes
Add and remove repositoryNoInherits original permissionYes
Manage organization gate policies and coding standardsNoYesYes
Configure organization default settings for Git provider integrationNoYesYes
Obtain audit logs for organization events4NoYesYes
Invite and accept members,
modify billing
NoNoYesOperationAllowed
Join organizationYes
View and follow private repositoryYes
Access Security and risk managementYes
Access AI Risk Hub OverviewYes
Access AI Risk Hub AI assets and Tools & workflowsYes
Ignore issues and files, configure code patterns, reanalyze branches and pull requestsInherits original permission
Upload coverage using an account API token, see the coverage report logsInherits original permission
Configure repository Git provider integration settingsInherits original permission
Configure repository quality gates and goalsInherits original permission
Configure repository to run analysis on a local build server, manage repository API tokensInherits original permission
Add and remove repositoryInherits original permission
Manage organization gate policies and coding standardsYes
Configure organization default settings for Git provider integrationYes
Obtain audit logs for organization events4Yes
Invite and accept members, modify billingNo
Assign and revoke the organization manager roleNo
+ +### Organization admin + + + - - - - + + + + + + + + + + + + + + + + + + + +
Assign and revoke the organization manager roleNoNoYesOperationAllowed
Join organizationYes1
View and follow private repositoryYes
Access Security and risk managementYes
Access AI Risk Hub OverviewYes
Access AI Risk Hub AI assets and Tools & workflowsYes
Ignore issues and files, configure code patterns, reanalyze branches and pull requestsYes
Upload coverage using an account API token, see the coverage report logsYes
Configure repository Git provider integration settingsYes
Configure repository quality gates and goalsYes
Configure repository to run analysis on a local build server, manage repository API tokensYes
Add and remove repositoryYes
Manage organization gate policies and coding standardsYes
Configure organization default settings for Git provider integrationYes
Obtain audit logs for organization events4Yes
Invite and accept members, modify billingYes
Assign and revoke the organization manager roleYes
-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](changing-your-plan-and-billing.md#allowing-new-people-to-join-your-organization). -3: These users can only see security items originating from Codacy repositories that they follow. +1: Joining an organization may need an approval depending on your setting for [accepting new people](changing-your-plan-and-billing.md#allowing-new-people-to-join-your-organization). +2: These users can only see security items originating from Codacy repositories that they follow. +3: Requires that an organization owner has given the Codacy GitHub App access to the repositories to add or remove. 4: [Audit logs](./audit-logs-for-organizations.md) are available only on [Business plan](https://www.codacy.com/pricing). ## See also @@ -569,11 +276,6 @@ td:not(:first-child), th:not(:first-child) { text-align: center !important; } -/*Background color for row containing the Codacy permission levels*/ -table:not(data-exclude) tr:nth-child(1) td { - background-color: var(--docs-bg-brand); -} - /*Add vertical borders and disable horizontal borders*/ td { border-left: 1px solid var(--md-default-fg-color--lightest); From 4cd53f8c55a6d08224bfbf4ff56aec652c89a0cb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Wed, 12 Aug 2026 14:36:39 +0100 Subject: [PATCH 2/5] docs: merge per-role permission tables into one comparison matrix The five separate Operation|Allowed tables made it hard to compare roles side by side, which is the more common use case (an admin deciding what role to assign) than looking up a single role. Replaces them with one table (Operation rows x 5 Codacy-role columns) so all roles are visible at once, still narrower than the original per-provider tables. Anchors for each role are preserved via id attributes on the table header cells. Co-Authored-By: Claude Sonnet 5 --- ...roles-and-permissions-for-organizations.md | 158 +++--------------- 1 file changed, 22 insertions(+), 136 deletions(-) diff --git a/docs/organizations/roles-and-permissions-for-organizations.md b/docs/organizations/roles-and-permissions-for-organizations.md index fa5f64d9fc..abe9c129e9 100644 --- a/docs/organizations/roles-and-permissions-for-organizations.md +++ b/docs/organizations/roles-and-permissions-for-organizations.md @@ -112,150 +112,36 @@ Bitbucket has no role that maps to [Repository write](#repository-write) or [Rep ## Permissions by Codacy role -The tables below list what each Codacy role is allowed to do. These permissions are the same regardless of Git provider—see [Permissions for GitHub](#permissions-for-github), [Permissions for GitLab](#permissions-for-gitlab), or [Permissions for Bitbucket](#permissions-for-bitbucket) to find your Codacy role. - -### Repository read - - - - - - - - - - - - - - - - - - - - - - - - - - -
OperationAllowed
Join organizationYes1
View and follow private repositoryYes
Access Security and risk managementYes2
Access AI Risk Hub OverviewYes
Access AI Risk Hub AI assets and Tools & workflowsNo
Ignore issues and files, configure code patterns, reanalyze branches and pull requestsConfigurable
Upload coverage using an account API token, see the coverage report logsNo
Configure repository Git provider integration settingsNo
Configure repository quality gates and goalsNo
Configure repository to run analysis on a local build server, manage repository API tokensNo
Add and remove repositoryNo
Manage organization gate policies and coding standardsNo
Configure organization default settings for Git provider integrationNo
Obtain audit logs for organization events4No
Invite and accept members, modify billingNo
Assign and revoke the organization manager roleNo
- -### Repository write - - - - - - - - - - - - - - - - - - - - - - - - - - -
OperationAllowed
Join organizationYes1
View and follow private repositoryYes
Access Security and risk managementYes2
Access AI Risk Hub OverviewYes
Access AI Risk Hub AI assets and Tools & workflowsNo
Ignore issues and files, configure code patterns, reanalyze branches and pull requestsConfigurable
Upload coverage using an account API token, see the coverage report logsYes
Configure repository Git provider integration settingsNo
Configure repository quality gates and goalsNo
Configure repository to run analysis on a local build server, manage repository API tokensNo
Add and remove repositoryNo
Manage organization gate policies and coding standardsNo
Configure organization default settings for Git provider integrationNo
Obtain audit logs for organization events4No
Invite and accept members, modify billingNo
Assign and revoke the organization manager roleNo
- -### Repository admin - - - - - - - - - - - - - - - - - - - - - - - - - - -
OperationAllowed
Join organizationYes1
View and follow private repositoryYes
Access Security and risk managementYes2
Access AI Risk Hub OverviewYes
Access AI Risk Hub AI assets and Tools & workflowsNo
Ignore issues and files, configure code patterns, reanalyze branches and pull requestsYes
Upload coverage using an account API token, see the coverage report logsYes
Configure repository Git provider integration settingsYes
Configure repository quality gates and goalsYes
Configure repository to run analysis on a local build server, manage repository API tokensYes
Add and remove repositoryYes3
Manage organization gate policies and coding standardsNo
Configure organization default settings for Git provider integrationNo
Obtain audit logs for organization events4No
Invite and accept members, modify billingNo
Assign and revoke the organization manager roleNo
- -### Organization manager - - - - - - - - - - - - - - - - - - - - - - - - - - -
OperationAllowed
Join organizationYes
View and follow private repositoryYes
Access Security and risk managementYes
Access AI Risk Hub OverviewYes
Access AI Risk Hub AI assets and Tools & workflowsYes
Ignore issues and files, configure code patterns, reanalyze branches and pull requestsInherits original permission
Upload coverage using an account API token, see the coverage report logsInherits original permission
Configure repository Git provider integration settingsInherits original permission
Configure repository quality gates and goalsInherits original permission
Configure repository to run analysis on a local build server, manage repository API tokensInherits original permission
Add and remove repositoryInherits original permission
Manage organization gate policies and coding standardsYes
Configure organization default settings for Git provider integrationYes
Obtain audit logs for organization events4Yes
Invite and accept members, modify billingNo
Assign and revoke the organization manager roleNo
- -### Organization admin +The table below compares what each Codacy role is allowed to do. These permissions are the same regardless of Git provider—see [Permissions for GitHub](#permissions-for-github), [Permissions for GitLab](#permissions-for-gitlab), or [Permissions for Bitbucket](#permissions-for-bitbucket) to find your Codacy role. - + + + + + - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + +
OperationAllowedRepository readRepository writeRepository adminOrganization managerOrganization admin
Join organizationYes1
View and follow private repositoryYes
Access Security and risk managementYes
Access AI Risk Hub OverviewYes
Access AI Risk Hub AI assets and Tools & workflowsYes
Ignore issues and files, configure code patterns, reanalyze branches and pull requestsYes
Upload coverage using an account API token, see the coverage report logsYes
Configure repository Git provider integration settingsYes
Configure repository quality gates and goalsYes
Configure repository to run analysis on a local build server, manage repository API tokensYes
Add and remove repositoryYes
Manage organization gate policies and coding standardsYes
Configure organization default settings for Git provider integrationYes
Obtain audit logs for organization events4Yes
Invite and accept members, modify billingYes
Assign and revoke the organization manager roleYes
Join organizationYes1Yes1Yes1YesYes1
View and follow private repositoryYesYesYesYesYes
Access Security and risk managementYes2Yes2Yes2YesYes
Access AI Risk Hub OverviewYesYesYesYesYes
Access AI Risk Hub AI assets and Tools & workflowsNoNoNoYesYes
Ignore issues and files, configure code patterns, reanalyze branches and pull requestsConfigurableConfigurableYesInherits original permissionYes
Upload coverage using an account API token, see the coverage report logsNoYesYesInherits original permissionYes
Configure repository Git provider integration settingsNoNoYesInherits original permissionYes
Configure repository quality gates and goalsNoNoYesInherits original permissionYes
Configure repository to run analysis on a local build server, manage repository API tokensNoNoYesInherits original permissionYes
Add and remove repositoryNoNoYes3Inherits original permissionYes
Manage organization gate policies and coding standardsNoNoNoYesYes
Configure organization default settings for Git provider integrationNoNoNoYesYes
Obtain audit logs for organization events4NoNoNoYesYes
Invite and accept members, modify billingNoNoNoNoYes
Assign and revoke the organization manager roleNoNoNoNoYes
From cb3834a5d85008bdef3da7340bb49bea2021cd72 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Wed, 12 Aug 2026 14:44:07 +0100 Subject: [PATCH 3/5] docs: use tables for the Git provider role mappings Bulleted lists forced a comma-separated set of provider roles into a bolded "term," which is an awkward fit for a plain role-to-role mapping. A two-column table (Git provider role | Codacy role) is the more direct container for that comparison. Co-Authored-By: Claude Sonnet 5 --- ...roles-and-permissions-for-organizations.md | 36 +++++++++++-------- 1 file changed, 21 insertions(+), 15 deletions(-) diff --git a/docs/organizations/roles-and-permissions-for-organizations.md b/docs/organizations/roles-and-permissions-for-organizations.md index abe9c129e9..0860f70fbb 100644 --- a/docs/organizations/roles-and-permissions-for-organizations.md +++ b/docs/organizations/roles-and-permissions-for-organizations.md @@ -76,12 +76,14 @@ To revoke the organization manager role: The following GitHub Cloud and GitHub Enterprise roles map to these Codacy roles: -- **Outside collaborator1:** not supported as a Codacy role -- **Repository read, Repository triage:** [Repository read](#repository-read) -- **Repository write, Repository maintain:** [Repository write](#repository-write) -- **Repository admin:** [Repository admin](#repository-admin) -- **No GitHub role maps here—assigned directly on Codacy:** [Organization manager](#organization-manager) -- **Organization Owner:** [Organization admin](#organization-admin) +| GitHub role | Codacy role | +|---|---| +| Outside collaborator1 | Not supported as a Codacy role | +| Repository read, Repository triage | [Repository read](#repository-read) | +| Repository write, Repository maintain | [Repository write](#repository-write) | +| Repository admin | [Repository admin](#repository-admin) | +| — (assigned directly on Codacy) | [Organization manager](#organization-manager) | +| Organization Owner | [Organization admin](#organization-admin) | 1: Outside collaborators aren't supported as members of organizations on Codacy. You can still [add outside collaborators to Codacy](managing-people.md#adding-people) so that Codacy analyzes their commits to private repositories, but they won't be able to join your Codacy organization. @@ -89,12 +91,14 @@ The following GitHub Cloud and GitHub Enterprise roles map to these Codacy roles The following GitLab Cloud and GitLab Enterprise roles map to these Codacy roles: -- **External user1:** not supported as a Codacy role -- **Project guest, Project reporter:** [Repository read](#repository-read) -- **Project developer:** [Repository write](#repository-write) -- **Project maintainer, Project owner:** [Repository admin](#repository-admin) -- **No GitLab role maps here—assigned directly on Codacy:** [Organization manager](#organization-manager) -- **Group owner, Administrator:** [Organization admin](#organization-admin) +| GitLab role | Codacy role | +|---|---| +| External user1 | Not supported as a Codacy role | +| Project guest, Project reporter | [Repository read](#repository-read) | +| Project developer | [Repository write](#repository-write) | +| Project maintainer, Project owner | [Repository admin](#repository-admin) | +| — (assigned directly on Codacy) | [Organization manager](#organization-manager) | +| Group owner, Administrator | [Organization admin](#organization-admin) | 1: External users aren't supported as members of organizations on Codacy. You can still [add external users to Codacy](managing-people.md#adding-people) so that Codacy analyzes their commits to private repositories, but they won't be able to join your Codacy organization. @@ -102,9 +106,11 @@ The following GitLab Cloud and GitLab Enterprise roles map to these Codacy roles The following Bitbucket Cloud and Bitbucket Server roles map to these Codacy roles: -- **Read, Write1:** [Repository read](#repository-read) -- **No Bitbucket role maps here—assigned directly on Codacy:** [Organization manager](#organization-manager) -- **Admin:** [Organization admin](#organization-admin) +| Bitbucket role | Codacy role | +|---|---| +| Read, Write1 | [Repository read](#repository-read) | +| — (assigned directly on Codacy) | [Organization manager](#organization-manager) | +| Admin | [Organization admin](#organization-admin) | Bitbucket has no role that maps to [Repository write](#repository-write) or [Repository admin](#repository-admin). From ded5dbdb84aa9c6fa977c714851d611f4296ac63 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Wed, 12 Aug 2026 14:50:33 +0100 Subject: [PATCH 4/5] docs: scope the GitHub App footnote to GitHub The footnote on "Add and remove repository" only existed on the original GitHub table; GitLab and Bitbucket's identical Yes had no such caveat. Merging the three provider tables into one shared Repository admin column left the footnote attached to a value GitLab/Bitbucket readers also see, so make the scope explicit rather than let it read as a cross-provider requirement. Co-Authored-By: Claude Sonnet 5 --- docs/organizations/roles-and-permissions-for-organizations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/organizations/roles-and-permissions-for-organizations.md b/docs/organizations/roles-and-permissions-for-organizations.md index 0860f70fbb..3f3039f927 100644 --- a/docs/organizations/roles-and-permissions-for-organizations.md +++ b/docs/organizations/roles-and-permissions-for-organizations.md @@ -153,7 +153,7 @@ The table below compares what each Codacy role is allowed to do. These permissio 1: Joining an organization may need an approval depending on your setting for [accepting new people](changing-your-plan-and-billing.md#allowing-new-people-to-join-your-organization). 2: These users can only see security items originating from Codacy repositories that they follow. -3: Requires that an organization owner has given the Codacy GitHub App access to the repositories to add or remove. +3: On GitHub, requires that an organization owner has given the Codacy GitHub App access to the repositories to add or remove. 4: [Audit logs](./audit-logs-for-organizations.md) are available only on [Business plan](https://www.codacy.com/pricing). ## See also From b629a8d4b497adea200e44c466913205fed4f135 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Wed, 12 Aug 2026 15:44:57 +0100 Subject: [PATCH 5/5] fix: correct table border CSS comment and include th in border rules The comment said borders were "disabled" for horizontal lines when the rule actually adds them via border-top. th was also missing from the selector, so header cells lacked the vertical dividers body cells get. Addresses Codacy AI review feedback on #2732. Co-Authored-By: Claude Sonnet 5 --- .../roles-and-permissions-for-organizations.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/organizations/roles-and-permissions-for-organizations.md b/docs/organizations/roles-and-permissions-for-organizations.md index 3f3039f927..914a8dc002 100644 --- a/docs/organizations/roles-and-permissions-for-organizations.md +++ b/docs/organizations/roles-and-permissions-for-organizations.md @@ -168,12 +168,12 @@ td:not(:first-child), th:not(:first-child) { text-align: center !important; } -/*Add vertical borders and disable horizontal borders*/ -td { +/*Add vertical and horizontal borders between cells*/ +th, td { border-left: 1px solid var(--md-default-fg-color--lightest); border-top: 1px solid var(--md-default-fg-color--lightest); } -td:nth-child(1) { +th:nth-child(1), td:nth-child(1) { border-left: 0; }