From 21c5bb40fdcde00c76e4f8abe9dd893a8d93fd52 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Mon, 16 Nov 2026 12:48:47 +0000 Subject: [PATCH 1/2] fix: DAST permissions say admins or organization managers The DAST API example said Git provider admin only in three places, contradicting its own intro and the code. The app-scanning note said DAST findings are visible to admins only; organization managers see them too. Co-Authored-By: Claude Opus 5.5 --- docs/codacy-api/examples/triggering-dast-scans.md | 6 +++--- docs/security/app-scanning.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/codacy-api/examples/triggering-dast-scans.md b/docs/codacy-api/examples/triggering-dast-scans.md index 6bb45af2a8..e4ad6e9443 100644 --- a/docs/codacy-api/examples/triggering-dast-scans.md +++ b/docs/codacy-api/examples/triggering-dast-scans.md @@ -74,7 +74,7 @@ Replace the placeholders with your own values: |-------|----------|-------------| | **API_KEY** | true | [Account API token](../api-tokens.md#account-api-tokens) used to authenticate on the Codacy API | | **GIT_PROVIDER** | true | Git provider hosting of the organization, using one of the values in the table below.
**Options:** `gh` (GitHub Cloud), `ghe`(GitHub Enterprise), `gl` (Gitlab Cloud), `gle` (Gitlab Enterprise), `bb` (Bitbucket Cloud), `bbe` (Bitbucket Server) | -| **ORGANIZATION** | true | Name of the organization on the Git provider. You must have admin permissions over the organization on the Git provider.
For example, `codacy` | +| **ORGANIZATION** | true | Name of the organization on the Git provider. You must be an admin of the organization on the Git provider or an organization manager on Codacy.
For example, `codacy` | | **TARGET_URL** | true | URL of the Web app or API that will be scanned.
Must start with `http://` or `https://`
For example, `https://api.codacy.com/v1`| | **TARGET_TYPE** | false | Type of target to be scanned
**Options:** `webapp` (default), `openapi` or `graphql`| | **API_DEFINITION_URL** | false * | The URL to a publicly accessible OpenAPI specification.
*** Required for OpenAPI targets**| @@ -104,8 +104,8 @@ Replace the placeholders with your own values: - **API_KEY:** [Account API token](../api-tokens.md#account-api-tokens) used to authenticate on the Codacy API. - **GIT_PROVIDER:** Git provider hosting of the organization (check the table on the example above). For example, `gh` for GitHub Cloud. -- **ORGANIZATION:** Name of the organization on the Git provider. For example, `codacy`. You must have admin permissions over the organization on the Git provider. -- **DAST_TARGET_ID:** Identifier of a DAST target to analyze (obtained in the [previous section](./triggering-dast-scans.md#creating-targets). For example, `457`. You must have admin permissions over the organization on the Git provider. +- **ORGANIZATION:** Name of the organization on the Git provider. For example, `codacy`. You must be an admin of the organization on the Git provider or an organization manager on Codacy. +- **DAST_TARGET_ID:** Identifier of a DAST target to analyze (obtained in the [previous section](./triggering-dast-scans.md#creating-targets). For example, `457`. You must be an admin of the organization on the Git provider or an organization manager on Codacy. Scans occur asynchronously. To monitor an ongoing scan you can use the [target management page in Codacy](../../security/app-scanning.md#app-scanning). Once completed, you can access all scan results by navigating to the **Security dashboard**, selecting the **Findings tab** and filtering by **Scan types > DAST/App scanning**, or by clicking on a configured target to expand all of that target's results. Additionaly, you can use the `SearchSRMItems` endpoint to filter findings by their DAST target URL with the following request: diff --git a/docs/security/app-scanning.md b/docs/security/app-scanning.md index a79c08118d..f17703999d 100644 --- a/docs/security/app-scanning.md +++ b/docs/security/app-scanning.md @@ -215,7 +215,7 @@ Once a scan completes, results will be available under the **Findings** tab. Use Failed scans are retried based on the failure reason. Retries are added back to the queue automatically and processed when capacity allows. !!! note - Currently, DAST findings are only visible to admin and organization admin roles. + Admins and organization managers can see all DAST findings. Other members only see security items from repositories they follow. See [roles and permissions for organizations](../organizations/roles-and-permissions-for-organizations.md). ## Findings results for your DAST scans From 52b7a931fe510fdcb85b4b3903e61891e32c39f3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Mon, 16 Nov 2026 12:55:01 +0000 Subject: [PATCH 2/2] fix: DAST note says members only see findings from linked repositories srm-service filters member results with repository_id = ANY(...), so findings from targets with no linked repository never reach members. Co-Authored-By: Claude Opus 5.5 --- docs/security/app-scanning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/security/app-scanning.md b/docs/security/app-scanning.md index f17703999d..ef646f83d7 100644 --- a/docs/security/app-scanning.md +++ b/docs/security/app-scanning.md @@ -215,7 +215,7 @@ Once a scan completes, results will be available under the **Findings** tab. Use Failed scans are retried based on the failure reason. Retries are added back to the queue automatically and processed when capacity allows. !!! note - Admins and organization managers can see all DAST findings. Other members only see security items from repositories they follow. See [roles and permissions for organizations](../organizations/roles-and-permissions-for-organizations.md). + Only admins and organization managers can create targets and see all DAST findings. Other members only see findings from targets linked to a repository they follow. See [roles and permissions for organizations](../organizations/roles-and-permissions-for-organizations.md). ## Findings results for your DAST scans