From 3626780e6dd8eb3ff3d79affbce7cfef3b9b12bf Mon Sep 17 00:00:00 2001 From: Paul Osinski Date: Tue, 13 Oct 2026 15:51:59 -0400 Subject: [PATCH] docs(connectors): a connector's label can be renamed after creation The Pro connectors API now accepts a label change on an existing configuration and keeps every mapped Record linked to its Engagement by ID, so the docs stop implying the label is fixed and spell out that renaming it neither moves nor duplicates the Engagements and Tests the connector already created. Co-Authored-By: Claude Fable 5.1 --- docs/content/connectors/upstream/add_edit.md | 2 +- docs/content/connectors/upstream/manage_records.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/connectors/upstream/add_edit.md b/docs/content/connectors/upstream/add_edit.md index 8493c79552..1c1085a0f0 100644 --- a/docs/content/connectors/upstream/add_edit.md +++ b/docs/content/connectors/upstream/add_edit.md @@ -24,7 +24,7 @@ You can also edit an existing Connector under the **Configured Connectors** head 4. You will need an accessible **Location URL** for the tool, along with an API **Secret** key. The location of the API key will depend on the tool you are trying to configure. See our [Tool\-Specific Reference](../../toolreference/upstream/) for more details. ​ -5. Set a **Label** for this connection to help you identify it in DefectDojo. +5. Set a **Label** for this connection to help you identify it in DefectDojo. The label is cosmetic: you can rename it later from **Edit Configuration** without affecting the Records, Engagements or Tests the connector has already created. Each connector type can only use a given label once. ​ 6. Schedule the Connector's automatic discovery and sync under the **Discovery Configuration** and **Synchronization Configuration** sections. For each, pick a **Frequency** (every 6, 12, or 24 hours) and a **Time**. At *Every 24 hours* the connector runs once a day at that time; at *Every 6 hours* or *Every 12 hours* the time sets when the first run of the day happens, and the connector repeats from there. Times are shown in your browser's local timezone. You can change any of this later. ​ diff --git a/docs/content/connectors/upstream/manage_records.md b/docs/content/connectors/upstream/manage_records.md index 2fb1881a35..cbcbac3154 100644 --- a/docs/content/connectors/upstream/manage_records.md +++ b/docs/content/connectors/upstream/manage_records.md @@ -127,7 +127,7 @@ Once a Record is Mapped, DefectDojo will be ready to import your tool’s scans * Record Mappings are designed to be non-invasive. If you map an Asset to a Record which contains existing Engagements or Findings, those existing Engagements and Findings will not be affected or overwritten by the data sync process. ​ -* All data created via a connector will be stored under a single Engagement called **Global Connectors**. That Engagement will create a separate Test for each Connector mapped to the Asset. +* All data created via a connector will be stored under a single Engagement named **Global Connectors - \ - \**. That Engagement will create a separate Test for each Connector mapped to the Asset. The Record stays linked to that Engagement by ID, not by name: renaming the Connector's label does not create a new Engagement, and syncs keep landing in the existing one under its original name. ![image](images/manage_records_2.jpg)