diff --git a/docs/organizations/managing-security-and-risk.md b/docs/organizations/managing-security-and-risk.md
index 29bb951a24..012ab74335 100644
--- a/docs/organizations/managing-security-and-risk.md
+++ b/docs/organizations/managing-security-and-risk.md
@@ -107,7 +107,7 @@ To export a list of findings as a CSV file, click the options menu in the top ri
 
 ## Reviewing severity rules and integration settings {: id="reviewing-settings"}
 
-To review the [severity assignment rules](#item-severities-and-deadlines) or the [Jira integration settings](./integrations/jira-integration.md), click the options menu in the top right-hand corner of the page and select respectively **See severity rules** or **View integrations**.
+To [review the severity assignment rules](#item-severities-and-deadlines) or [manage the Jira integration](./integrations/jira-integration.md), click the options menu in the top right-hand corner of the page and select respectively **See severity rules** or **Manage Jira integration**.<!-- TODO TAROT-2591 confirm link and button caption update for Jira integration -->
 
 ## How Codacy manages findings {: id="opening-and-closing-items"}
 
@@ -201,6 +201,9 @@ The following table describes how finding statuses map to deadlines:
 
 ## Finding severities and deadlines {: id="item-severities-and-deadlines"}
 
+!!! note
+    Currently, Codacy doesn't support customizing the severity rules for security findings.
+
 The following table defines finding severities and days to fix the associated security issue, based on the importance of the underlying issue:
 
 | Finding<br/>severity | <br/>Days to fix | Underlying Codacy<br/>issue severity | Underlying Jira<br/>issue priority <sup>1</sup> |