From 3741201b87101999183b48f6d89c4c103260001e Mon Sep 17 00:00:00 2001
From: Sheen Capadngan <sheensantoscapadngan@gmail.com>
Date: Sat, 15 Mar 2025 01:55:57 +0800
Subject: [PATCH] misc: update legacy system description

---
 .../UpgradePrivilegeSystemModal.tsx                        | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/frontend/src/pages/organization/AccessManagementPage/components/UpgradePrivilegeSystemModal/UpgradePrivilegeSystemModal.tsx b/frontend/src/pages/organization/AccessManagementPage/components/UpgradePrivilegeSystemModal/UpgradePrivilegeSystemModal.tsx
index 05deb45d0..8a6620777 100644
--- a/frontend/src/pages/organization/AccessManagementPage/components/UpgradePrivilegeSystemModal/UpgradePrivilegeSystemModal.tsx
+++ b/frontend/src/pages/organization/AccessManagementPage/components/UpgradePrivilegeSystemModal/UpgradePrivilegeSystemModal.tsx
@@ -88,9 +88,10 @@ export const UpgradePrivilegeSystemModal = ({ isOpen, onOpenChange }: Props) =>
               <div className="mb-3 ml-7">
                 <p className="mb-3">
                   <strong>Legacy system:</strong> Users with higher privilege levels could modify
-                  access for anyone below them. This limits accountability and makes it impossible
-                  to allow specialized roles (like team leads) to manage their team&apos;s access
-                  without granting them broader administrative powers.
+                  access for anyone below them. This rigid hierarchy makes it difficult to implement
+                  precise access control policies, forcing you to either over-grant permissions or
+                  create complex workarounds when specialized roles (like team leads) need to manage
+                  their team&apos;s access without receiving broader administrative powers.
                 </p>
                 <p>
                   <strong>New system:</strong> Users need explicit permission to modify specific