From 3ca6c0971052115b9f52ab0374089fcdae6b789f Mon Sep 17 00:00:00 2001
From: sr-remsha <46220620+sr-remsha@users.noreply.github.com>
Date: Tue, 28 Nov 2023 12:29:15 +0100
Subject: [PATCH] Update roles-management.md

---
 docs/tutorials/roles-management.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/tutorials/roles-management.md b/docs/tutorials/roles-management.md
index f576ab66..163902ba 100644
--- a/docs/tutorials/roles-management.md
+++ b/docs/tutorials/roles-management.md
@@ -67,7 +67,7 @@ In **Groups**, do the roles mapping for each group:
 
 The last step is to assign KeyCloak roles to AI DIAL core deployments: Applications, Addons, Assistants and Models.
 
-> Refer to [AI DIAL Configuration](/docs/Deployment/configuration.md) to learn more.
+> Refer to [AI DIAL Configuration](/docs/Deployment/configuration.md#proxyconfigjson-parameter) to learn more.
 
 ```yaml
 "addons": {
@@ -181,7 +181,7 @@ AzureProvider({
 
 The last step is to assign Microsoft Azure AD groups to AI DIAL Core deployments: Applications, Addons, Assistants and Models.
 
-> Refer to [AI DIAL Configuration](/docs/Deployment/configuration.md) to learn more.
+> Refer to [AI DIAL Configuration](/docs/Deployment/configuration.md#proxyconfigjson-parameter) to learn more.
 
 > **Note**: in the example below, MS Azure groups are mapped to AI DIAL Core user roles one to one.