From 41dbe7de4e886340b411f5bab452b9d0f449e76b Mon Sep 17 00:00:00 2001
From: Jon Ayers <jon@coder.com>
Date: Tue, 12 Dec 2023 08:24:04 -0600
Subject: [PATCH] fix: use correct permission when determining orphan deletion
 privileges (#11143)

---
 site/src/pages/WorkspacePage/WorkspaceReadyPage.tsx | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/site/src/pages/WorkspacePage/WorkspaceReadyPage.tsx b/site/src/pages/WorkspacePage/WorkspaceReadyPage.tsx
index 77b3f9d0d5..67f40ef0f7 100644
--- a/site/src/pages/WorkspacePage/WorkspaceReadyPage.tsx
+++ b/site/src/pages/WorkspacePage/WorkspaceReadyPage.tsx
@@ -168,8 +168,9 @@ export const WorkspaceReadyPage = ({
     updateWorkspace(workspace, queryClient),
   );
 
-  // Delete workspace
-  const canDeleteWorkspace = Boolean(permissions?.updateWorkspace);
+  // If a user can update the template then they can force a delete
+  // (via orphan).
+  const canUpdateTemplate = Boolean(permissions?.updateTemplate);
   const [isConfirmingDelete, setIsConfirmingDelete] = useState(false);
   const deleteWorkspaceMutation = useMutation(
     deleteWorkspace(workspace, queryClient),
@@ -304,7 +305,7 @@ export const WorkspaceReadyPage = ({
 
       <WorkspaceDeleteDialog
         workspace={workspace}
-        canUpdateTemplate={canDeleteWorkspace}
+        canUpdateTemplate={canUpdateTemplate}
         isOpen={isConfirmingDelete}
         onCancel={() => {
           setIsConfirmingDelete(false);