fix: disabled integration lead buttons when user doesn't have edit ac…

…cess (#513) (#514)
clevercanary · Jan 4, 2025 · 9d2a0a9 · 9d2a0a9
1 parent d03023f
commit 9d2a0a9
Showing 1 changed file with 5 additions and 0 deletions.
diff --git a/...nents/Forms/components/Atlas/components/IntegrationLeadSection/integrationLeadSection.tsx b/...nents/Forms/components/Atlas/components/IntegrationLeadSection/integrationLeadSection.tsx
@@ -48,6 +48,9 @@ export const IntegrationLeadSection = <
   getNewValue,
   integrationLeadName,
 }: IntegrationLeadSectionProps<T, TFieldArrayName, R>): JSX.Element => {
+  const {
+    formStatus: { isReadOnly },
+  } = formManager;
   const { append, fields, remove } = useFieldArray({
     control: formMethod.control,
     name: integrationLeadName,
@@ -75,6 +78,7 @@ export const IntegrationLeadSection = <
                 <IconButton
                   {...ICON_BUTTON_PROPS}
                   onClick={() => remove(index)}
+                  disabled={isReadOnly}
                 >
                   <DeleteIcon {...SVG_ICON_PROPS} />
                 </IconButton>
@@ -87,6 +91,7 @@ export const IntegrationLeadSection = <
         {...BUTTON_PROPS}
         startIcon={<AddIcon />}
         onClick={() => append(getNewValue())}
+        disabled={isReadOnly}
       >
         Add lead
       </StyledButton>