diff --git a/README.md b/README.md
index d8934794..8e8f4599 100644
--- a/README.md
+++ b/README.md
@@ -174,7 +174,7 @@ azd up
     - The container already starts Gunicorn through `application/single_app/Dockerfile`.
 - If your environment needs private or self-signed certificate authorities for outbound TLS checks to internal services, add them during image build using [docs/how-to/docker_customization.md](docs/how-to/docker_customization.md).
 
-## Native Python
+### Native Python
 - For **native Python App Service** deployments, deploy the `application/single_app` folder and set the App Service Startup command explicitly.
 
 Native Python deployment references:
diff --git a/application/single_app/functions_settings.py b/application/single_app/functions_settings.py
index 8afcd940..577bb676 100644
--- a/application/single_app/functions_settings.py
+++ b/application/single_app/functions_settings.py
@@ -215,6 +215,7 @@ def get_settings(use_cosmos=False, include_source=False):
         'enable_support_send_feedback': True,
         'support_feedback_recipient_email': '',
         'enable_support_latest_features': True,
+        'enable_support_latest_feature_documentation_links': False,
         'support_latest_features_visibility': get_default_support_latest_features_visibility(),
 
         # Enhanced Citations
diff --git a/application/single_app/route_frontend_admin_settings.py b/application/single_app/route_frontend_admin_settings.py
index 4656a1a4..94053752 100644
--- a/application/single_app/route_frontend_admin_settings.py
+++ b/application/single_app/route_frontend_admin_settings.py
@@ -13,6 +13,8 @@
 from admin_settings_int_utils import safe_int_with_source
 from support_menu_config import (
     get_support_latest_feature_catalog,
+    get_support_latest_feature_release_groups,
+    get_support_latest_feature_release_groups_for_settings,
     has_visible_support_latest_features,
     normalize_support_latest_features_visibility,
 )
@@ -123,6 +125,8 @@ def admin_settings():
             settings['support_feedback_recipient_email'] = ''
         if 'enable_support_latest_features' not in settings:
             settings['enable_support_latest_features'] = True
+        if 'enable_support_latest_feature_documentation_links' not in settings:
+            settings['enable_support_latest_feature_documentation_links'] = False
         settings['support_latest_features_visibility'] = normalize_support_latest_features_visibility(
             settings.get('support_latest_features_visibility', {})
         )
@@ -368,6 +372,8 @@ def admin_settings():
                 latest_version=latest_version,
                 download_url=download_url,
                 support_latest_feature_catalog=get_support_latest_feature_catalog(),
+                support_latest_feature_release_groups=get_support_latest_feature_release_groups(),
+                support_latest_feature_release_groups_preview=get_support_latest_feature_release_groups_for_settings(settings),
                 chunk_size_defaults=get_chunk_size_defaults(),
                 chunk_size_settings=settings.get('chunk_size', {}),
                 chunk_size_cap=get_chunk_size_cap(settings),
@@ -566,6 +572,9 @@ def parse_admin_int(raw_value, fallback_value, field_name="unknown", hard_defaul
                 enable_support_send_feedback = False
 
             enable_support_latest_features = form_data.get('enable_support_latest_features') == 'on'
+            enable_support_latest_feature_documentation_links = (
+                form_data.get('enable_support_latest_feature_documentation_links') == 'on'
+            )
             support_latest_features_visibility = {}
             for feature in get_support_latest_feature_catalog():
                 field_name = f"support_latest_feature_{feature['id']}"
@@ -1210,6 +1219,7 @@ def is_valid_url(url):
                 'enable_support_send_feedback': enable_support_send_feedback,
                 'support_feedback_recipient_email': support_feedback_recipient_email,
                 'enable_support_latest_features': enable_support_latest_features,
+                'enable_support_latest_feature_documentation_links': enable_support_latest_feature_documentation_links,
                 'support_latest_features_visibility': support_latest_features_visibility,
 
                 # Enhanced Citations
diff --git a/application/single_app/route_frontend_support.py b/application/single_app/route_frontend_support.py
index b6549457..668fb684 100644
--- a/application/single_app/route_frontend_support.py
+++ b/application/single_app/route_frontend_support.py
@@ -4,7 +4,10 @@
 from functions_authentication import *
 from functions_settings import *
 from swagger_wrapper import swagger_route, get_auth_security
-from support_menu_config import get_visible_support_latest_features
+from support_menu_config import (
+    get_visible_support_latest_feature_groups,
+    get_visible_support_latest_features,
+)
 
 
 def _support_menu_access_allowed():
@@ -30,9 +33,21 @@ def support_latest_features():
             return 'Not Found', 404
 
         visible_features = get_visible_support_latest_features(settings)
+        visible_feature_groups = get_visible_support_latest_feature_groups(settings)
+        current_release_features = []
+        previous_release_feature_groups = []
+
+        for feature_group in visible_feature_groups:
+            if feature_group.get('id') == 'current_release':
+                current_release_features = feature_group.get('features', [])
+            else:
+                previous_release_feature_groups.append(feature_group)
+
         return render_template(
             'latest_features.html',
-            support_latest_features=visible_features,
+            support_latest_features=current_release_features or visible_features,
+            support_latest_feature_groups=visible_feature_groups,
+            support_previous_release_feature_groups=previous_release_feature_groups,
         )
 
     @app.route('/support/send-feedback')
diff --git a/application/single_app/static/images/features/chat_tags_including_doc_classification.png b/application/single_app/static/images/features/chat_tags_including_doc_classification.png
new file mode 100644
index 00000000..445714b1
Binary files /dev/null and b/application/single_app/static/images/features/chat_tags_including_doc_classification.png differ
diff --git a/application/single_app/static/images/features/conversation_export.png b/application/single_app/static/images/features/conversation_export.png
new file mode 100644
index 00000000..7cfcd88e
Binary files /dev/null and b/application/single_app/static/images/features/conversation_export.png differ
diff --git a/application/single_app/static/images/features/conversation_export_type_option.png b/application/single_app/static/images/features/conversation_export_type_option.png
new file mode 100644
index 00000000..3cdc7d05
Binary files /dev/null and b/application/single_app/static/images/features/conversation_export_type_option.png differ
diff --git a/application/single_app/static/images/features/retention_policy-manage_group.png b/application/single_app/static/images/features/retention_policy-manage_group.png
new file mode 100644
index 00000000..f283dfa1
Binary files /dev/null and b/application/single_app/static/images/features/retention_policy-manage_group.png differ
diff --git a/application/single_app/static/images/features/retention_policy-personal_profile.png b/application/single_app/static/images/features/retention_policy-personal_profile.png
new file mode 100644
index 00000000..dd527335
Binary files /dev/null and b/application/single_app/static/images/features/retention_policy-personal_profile.png differ
diff --git a/application/single_app/static/images/features/workspace_grid_view.png b/application/single_app/static/images/features/workspace_grid_view.png
new file mode 100644
index 00000000..db3b2444
Binary files /dev/null and b/application/single_app/static/images/features/workspace_grid_view.png differ
diff --git a/application/single_app/static/images/features/workspace_scope_lock.png b/application/single_app/static/images/features/workspace_scope_lock.png
new file mode 100644
index 00000000..45af2688
Binary files /dev/null and b/application/single_app/static/images/features/workspace_scope_lock.png differ
diff --git a/application/single_app/static/images/features/workspace_scopes_in_chat.png b/application/single_app/static/images/features/workspace_scopes_in_chat.png
new file mode 100644
index 00000000..690deb67
Binary files /dev/null and b/application/single_app/static/images/features/workspace_scopes_in_chat.png differ
diff --git a/application/single_app/static/images/features/workspace_tags.png b/application/single_app/static/images/features/workspace_tags.png
new file mode 100644
index 00000000..4636c7a4
Binary files /dev/null and b/application/single_app/static/images/features/workspace_tags.png differ
diff --git a/application/single_app/static/js/chat/chat-documents.js b/application/single_app/static/js/chat/chat-documents.js
index dde90dc5..d0792db7 100644
--- a/application/single_app/static/js/chat/chat-documents.js
+++ b/application/single_app/static/js/chat/chat-documents.js
@@ -1323,6 +1323,74 @@ function syncTagsDropdownButtonText() {
   }
 }
 
+
+export async function ensureSearchDocumentsVisible() {
+  if (!searchDocumentsBtn || !searchDocumentsContainer) {
+    return false;
+  }
+
+  searchDocumentsBtn.classList.add('active');
+  searchDocumentsContainer.style.display = 'block';
+
+  if (scopeLocked === true) {
+    rebuildScopeDropdownWithLock();
+  } else {
+    buildScopeDropdown();
+  }
+
+  await loadAllDocs();
+  await loadTagsForScope();
+
+  try {
+    const dropdownInstance = bootstrap.Dropdown.getInstance(docDropdownButton);
+    if (dropdownInstance) {
+      dropdownInstance.update();
+    }
+  } catch (err) {
+    console.error('Error updating document dropdown:', err);
+  }
+
+  handleDocumentSelectChange();
+  return true;
+}
+
+
+function openDropdown(buttonElement) {
+  if (!buttonElement) {
+    return false;
+  }
+
+  try {
+    bootstrap.Dropdown.getOrCreateInstance(buttonElement, {
+      autoClose: 'outside'
+    }).show();
+    buttonElement.focus();
+    return true;
+  } catch (err) {
+    console.error('Error opening dropdown:', err);
+    return false;
+  }
+}
+
+
+export function openScopeDropdown() {
+  return openDropdown(scopeDropdownButton);
+}
+
+
+export function openTagsDropdown() {
+  if (!tagsDropdown || !tagsDropdownButton) {
+    return false;
+  }
+
+  if (tagsDropdown.style.display === 'none' && (!tagsDropdownItems || !tagsDropdownItems.children.length)) {
+    return false;
+  }
+
+  showTagsDropdown();
+  return openDropdown(tagsDropdownButton);
+}
+
 /* ---------------------------------------------------------------------------
    Get Selected Tags
 --------------------------------------------------------------------------- */
@@ -1541,27 +1609,7 @@ if (searchDocumentsBtn) {
     if (!searchDocumentsContainer) return;
 
     if (this.classList.contains("active")) {
-      searchDocumentsContainer.style.display = "block";
-      // Build the scope dropdown on first open (respect lock state)
-      if (scopeLocked === true) {
-        rebuildScopeDropdownWithLock();
-      } else {
-        buildScopeDropdown();
-      }
-      // Ensure initial population and state is correct when opening
-      loadAllDocs().then(() => {
-        // Load tags for the currently selected scope
-        loadTagsForScope();
-        // Update Bootstrap Popper positioning if dropdown was already initialized
-        try {
-          const dropdownInstance = bootstrap.Dropdown.getInstance(docDropdownButton);
-          if (dropdownInstance) {
-            dropdownInstance.update();
-          }
-        } catch (err) {
-          console.error("Error updating dropdown:", err);
-        }
-      });
+      ensureSearchDocumentsVisible();
     } else {
       searchDocumentsContainer.style.display = "none";
     }
diff --git a/application/single_app/static/js/chat/chat-onload.js b/application/single_app/static/js/chat/chat-onload.js
index d4ed6777..16de2096 100644
--- a/application/single_app/static/js/chat/chat-onload.js
+++ b/application/single_app/static/js/chat/chat-onload.js
@@ -2,7 +2,17 @@
 
 import { loadConversations, selectConversation, ensureConversationPresent, createNewConversation } from "./chat-conversations.js";
 // Import handleDocumentSelectChange
-import { loadAllDocs, populateDocumentSelectScope, handleDocumentSelectChange, loadTagsForScope, filterDocumentsBySelectedTags, setScopeFromUrlParam } from "./chat-documents.js";
+import {
+    loadAllDocs,
+    populateDocumentSelectScope,
+    handleDocumentSelectChange,
+    loadTagsForScope,
+    filterDocumentsBySelectedTags,
+    setScopeFromUrlParam,
+    ensureSearchDocumentsVisible,
+    openScopeDropdown,
+    openTagsDropdown,
+} from "./chat-documents.js";
 import { getUrlParameter } from "./chat-utils.js"; // Assuming getUrlParameter is in chat-utils.js now
 import { loadUserPrompts, loadGroupPrompts, initializePromptInteractions } from "./chat-prompts.js";
 import { initializeModelSelector, populateModelDropdown } from "./chat-model-selector.js";
@@ -13,6 +23,68 @@ import { initializeReasoningToggle } from "./chat-reasoning.js";
 import { initializeSpeechInput } from "./chat-speech-input.js";
 import { initChatTutorial } from "./chat-tutorial.js";
 
+
+function clearFeatureActionParam() {
+    const url = new URL(window.location.href);
+    if (!url.searchParams.has('feature_action')) {
+        return;
+    }
+
+    url.searchParams.delete('feature_action');
+    const nextUrl = `${url.pathname}${url.search}${url.hash}`;
+    window.history.replaceState({}, document.title, nextUrl);
+}
+
+
+function getFirstConversationId() {
+    const currentConversationId = window.chatConversations?.getCurrentConversationId?.();
+    if (currentConversationId) {
+        return currentConversationId;
+    }
+
+    const firstConversation = document.querySelector('.conversation-item[data-conversation-id]');
+    return firstConversation?.getAttribute('data-conversation-id') || null;
+}
+
+
+async function handleLatestFeatureLaunch(featureAction) {
+    switch (featureAction) {
+        case 'conversation_export': {
+            const conversationId = getFirstConversationId();
+            if (!conversationId) {
+                showToast('Open or start a conversation before exporting.', 'info');
+                return;
+            }
+
+            await ensureConversationPresent(conversationId);
+            await selectConversation(conversationId);
+
+            if (window.chatExport?.openExportWizard) {
+                window.chatExport.openExportWizard([conversationId], true);
+            } else {
+                showToast('Conversation export is not available right now.', 'warning');
+            }
+            return;
+        }
+        case 'multi_workspace_scope_management': {
+            await ensureSearchDocumentsVisible();
+            if (!openScopeDropdown()) {
+                showToast('Grounded-search scopes are not available right now.', 'info');
+            }
+            return;
+        }
+        case 'chat_document_and_tag_filtering': {
+            await ensureSearchDocumentsVisible();
+            if (!openTagsDropdown()) {
+                showToast('No tags are available yet for the current search scope.', 'info');
+            }
+            return;
+        }
+        default:
+            return;
+    }
+}
+
 window.addEventListener('DOMContentLoaded', async () => {
   console.log("DOM Content Loaded. Starting initializations."); // Log start
 
@@ -300,6 +372,17 @@ window.addEventListener('DOMContentLoaded', async () => {
           }
       }
 
+      const featureAction = getUrlParameter('feature_action') || '';
+      if (featureAction) {
+          try {
+              await handleLatestFeatureLaunch(featureAction);
+          } catch (err) {
+              console.error('Failed to handle latest-feature launch action:', err);
+          } finally {
+              clearFeatureActionParam();
+          }
+      }
+
       console.log("All initializations complete."); // Log end
 
   } catch (err) {
diff --git a/application/single_app/static/js/workspace/workspace-init.js b/application/single_app/static/js/workspace/workspace-init.js
index 145493fd..da541dc3 100644
--- a/application/single_app/static/js/workspace/workspace-init.js
+++ b/application/single_app/static/js/workspace/workspace-init.js
@@ -3,8 +3,37 @@
 // Make sure fetch functions are available globally or imported if using modules consistently
 // Assuming fetchUserDocuments and fetchUserPrompts are now globally available via window.* assignments in their respective files
 
-import { initializeTags } from './workspace-tags.js';
-import { initializeTagManagement } from './workspace-tag-management.js';
+import { initializeTags, setWorkspaceView } from './workspace-tags.js';
+import { initializeTagManagement, showTagManagementModal } from './workspace-tag-management.js';
+
+
+function clearFeatureActionParam() {
+    const url = new URL(window.location.href);
+    if (!url.searchParams.has('feature_action')) {
+        return;
+    }
+
+    url.searchParams.delete('feature_action');
+    window.history.replaceState({}, document.title, `${url.pathname}${url.search}${url.hash}`);
+}
+
+
+function handleWorkspaceFeatureAction() {
+    const params = new URLSearchParams(window.location.search);
+    const featureAction = params.get('feature_action') || '';
+
+    if (!featureAction) {
+        return;
+    }
+
+    if (featureAction === 'document_tag_system') {
+        showTagManagementModal();
+    } else if (featureAction === 'workspace_folder_view') {
+        setWorkspaceView('grid');
+    }
+
+    clearFeatureActionParam();
+}
 
 document.addEventListener('DOMContentLoaded', () => {
     console.log("Workspace initializing...");
@@ -51,4 +80,6 @@ document.addEventListener('DOMContentLoaded', () => {
         });
     });
 
+    handleWorkspaceFeatureAction();
+
 });
\ No newline at end of file
diff --git a/application/single_app/static/js/workspace/workspace-tags.js b/application/single_app/static/js/workspace/workspace-tags.js
index a8e8e705..8b1b2b13 100644
--- a/application/single_app/static/js/workspace/workspace-tags.js
+++ b/application/single_app/static/js/workspace/workspace-tags.js
@@ -165,6 +165,31 @@ function switchView(view) {
     }
 }
 
+
+export function setWorkspaceView(view) {
+    const normalizedView = view === 'grid' ? 'grid' : 'list';
+    const listRadio = document.getElementById('docs-view-list');
+    const gridRadio = document.getElementById('docs-view-grid');
+
+    if (normalizedView === 'grid') {
+        if (gridRadio) {
+            gridRadio.checked = true;
+        }
+        if (listRadio) {
+            listRadio.checked = false;
+        }
+    } else {
+        if (listRadio) {
+            listRadio.checked = true;
+        }
+        if (gridRadio) {
+            gridRadio.checked = false;
+        }
+    }
+
+    switchView(normalizedView);
+}
+
 // Update sort icons in the static grid control bar
 function updateGridSortIcons() {
     const bar = document.getElementById('grid-controls-bar');
diff --git a/application/single_app/support_menu_config.py b/application/single_app/support_menu_config.py
index 7fd469d0..d020daa8 100644
--- a/application/single_app/support_menu_config.py
+++ b/application/single_app/support_menu_config.py
@@ -4,6 +4,9 @@
 from copy import deepcopy
 
 
+_SUPPORT_LATEST_FEATURE_DOCS_SETTING_KEY = 'enable_support_latest_feature_documentation_links'
+
+
 _SUPPORT_LATEST_FEATURE_CATALOG = [
     {
         'id': 'guided_tutorials',
@@ -567,6 +570,332 @@
     },
 ]
 
+_SUPPORT_PREVIOUS_RELEASE_FEATURE_CATALOG = [
+    {
+        'id': 'conversation_export',
+        'title': 'Conversation Export',
+        'icon': 'bi-download',
+        'summary': 'Export one or multiple conversations from Chat in JSON or Markdown without carrying internal-only metadata into the downloaded package.',
+        'details': 'Conversation Export adds a guided workflow for choosing format, packaging, and download options when you need to reuse or archive chat history outside the app.',
+        'why': 'This matters because users often need to share, archive, or reuse a conversation without copying raw chat text by hand or exposing internal metadata that should stay inside SimpleChat.',
+        'guidance': [
+            'Open an existing conversation from Chat when you want to export content that already has enough context to share.',
+            'Choose JSON when you want a machine-readable export and Markdown when you want something easier for people to review directly.',
+            'Use the packaging options in the export flow when you need a cleaner handoff for reporting or project documentation.',
+        ],
+        'actions': [
+            {
+                'label': 'Open Conversation Export',
+                'description': 'Jump to Chat, open the first available conversation, and launch the export workflow directly.',
+                'href': '/chats?feature_action=conversation_export',
+                'icon': 'bi-box-arrow-in-right',
+            },
+            {
+                'label': 'Read Export Guide',
+                'description': 'Open the public release guide that walks through the conversation export workflow.',
+                'href': 'https://microsoft.github.io/simplechat/latest-release/export-conversation/',
+                'icon': 'bi-box-arrow-up-right',
+                'is_external': True,
+                'requires_settings': [_SUPPORT_LATEST_FEATURE_DOCS_SETTING_KEY],
+            },
+        ],
+        'images': [
+            {
+                'path': 'images/features/conversation_export.png',
+                'alt': 'Conversation export workflow screenshot',
+                'title': 'Conversation Export Workflow',
+                'caption': 'Primary export workflow showing how users can package and download conversation history.',
+                'label': 'Export Workflow',
+            },
+            {
+                'path': 'images/features/conversation_export_type_option.png',
+                'alt': 'Conversation export type option screenshot',
+                'title': 'Conversation Export Format Options',
+                'caption': 'Format selection options for choosing how conversation exports should be generated.',
+                'label': 'Format Options',
+            },
+        ],
+    },
+    {
+        'id': 'retention_policy',
+        'title': 'Retention Policy',
+        'icon': 'bi-hourglass-split',
+        'summary': 'Retention periods for conversations and documents can be configured with presets, organization defaults, or fully disabled automatic cleanup.',
+        'details': 'Retention Policy adds clearer controls for deciding how long conversations and documents should remain available before they are removed automatically.',
+        'why': 'This matters because teams often need predictable cleanup rules for compliance, storage hygiene, or operational consistency instead of manually pruning old content.',
+        'guidance': [
+            'Use the documented presets when you want a consistent retention window without manually calculating dates.',
+            'Choose the organization default when you want shared policy behavior across workspaces instead of one-off overrides.',
+            'Disable automatic deletion only when your environment has another retention process that already handles lifecycle management.',
+        ],
+        'actions': [
+            {
+                'label': 'Open Retention Settings',
+                'description': 'Open your profile page and jump to the retention policy settings section.',
+                'href': '/profile?feature_action=retention_policy#retention-policy-settings',
+                'icon': 'bi-box-arrow-in-right',
+            },
+            {
+                'label': 'Read Retention Guide',
+                'description': 'Open the public release guide for workspace and conversation retention controls.',
+                'href': 'https://microsoft.github.io/simplechat/latest-release/retention-policy/',
+                'icon': 'bi-box-arrow-up-right',
+                'is_external': True,
+                'requires_settings': [_SUPPORT_LATEST_FEATURE_DOCS_SETTING_KEY],
+            },
+        ],
+        'images': [
+            {
+                'path': 'images/features/retention_policy-personal_profile.png',
+                'alt': 'Personal retention policy profile settings screenshot',
+                'title': 'Personal Retention Settings',
+                'caption': 'Profile-based retention settings for personal conversations and documents.',
+                'label': 'Personal Profile Settings',
+            },
+            {
+                'path': 'images/features/retention_policy-manage_group.png',
+                'alt': 'Group retention policy management screenshot',
+                'title': 'Group Retention Management',
+                'caption': 'Group-level retention policy management for shared workspace content.',
+                'label': 'Manage Group Retention',
+            },
+        ],
+    },
+    {
+        'id': 'owner_only_group_agent_management',
+        'title': 'Owner-Only Group Agent Management',
+        'icon': 'bi-shield-lock',
+        'summary': 'Admins can restrict group agent and action management to the Owner role so other group roles stay read-only.',
+        'details': 'Owner-Only Group Agent Management adds a stricter governance option for teams that want group agents and actions maintained only by the group owner.',
+        'why': 'This matters because collaborative workspaces often need a smaller set of people with change authority, especially when group agents and connected actions affect many users at once.',
+        'guidance': [
+            'Use this when group ownership should be the only role that can change shared agents or actions.',
+            'Expect non-owner users to keep read access while creation, editing, and deletion move behind a stricter permission boundary.',
+            'If your environment relies on delegated group administrators, confirm that workflow before switching to owner-only enforcement.',
+        ],
+        'actions': [],
+    },
+    {
+        'id': 'enforce_workspace_scope_lock',
+        'title': 'Enforce Workspace Scope Lock',
+        'icon': 'bi-lock',
+        'summary': 'Admins can keep workspace scope locked after the first AI search so users do not accidentally mix sources mid-conversation.',
+        'details': 'Workspace Scope Lock prevents a conversation from drifting across personal, group, or public workspaces after the first grounded search has established the working scope.',
+        'why': 'This matters because cross-scope drift is hard to detect once a conversation is underway, and locking the scope protects against mixing evidence from the wrong workspace.',
+        'guidance': [
+            'Use this when your team wants stronger grounding discipline for workspace-scoped chat conversations.',
+            'Expect the lock to take effect after the first AI search in a conversation rather than before any prompt is sent.',
+            'If you train users to work across multiple scopes in the same session, document that this setting intentionally tightens that behavior.',
+        ],
+        'actions': [
+            {
+                'label': 'Read Scope Lock Guide',
+                'description': 'Open the public release guide for enforced workspace scope locking.',
+                'href': 'https://microsoft.github.io/simplechat/latest-release/workspace-scope-lock/',
+                'icon': 'bi-box-arrow-up-right',
+                'is_external': True,
+                'requires_settings': [_SUPPORT_LATEST_FEATURE_DOCS_SETTING_KEY],
+            },
+        ],
+        'images': [
+            {
+                'path': 'images/features/workspace_scope_lock.png',
+                'alt': 'Workspace scope lock screenshot',
+                'title': 'Workspace Scope Lock',
+                'caption': 'Locked workspace scope in chat after the first grounded search has established the evidence boundary.',
+                'label': 'Scope Lock',
+            },
+        ],
+    },
+    {
+        'id': 'document_tag_system',
+        'title': 'Document Tag System',
+        'icon': 'bi-tags',
+        'summary': 'Documents can be organized with color-coded tags across personal, group, and public workspaces, with AI search-aware filtering built in.',
+        'details': 'Document Tag System adds durable tag management, bulk tag workflows, and tag-aware search filtering so users can organize and target document sets more deliberately.',
+        'why': 'This matters because document-heavy workspaces become much easier to navigate when teams can classify content with reusable tags and then ask grounded questions against those tag groupings.',
+        'guidance': [
+            'Use tags when you want a lightweight way to organize documents without forcing everything into a rigid folder hierarchy.',
+            'Apply tags consistently across related documents so AI search filters can narrow results more cleanly during chat.',
+            'Revisit the shared guide if you want the combined tags, folder view, and chat filtering walkthrough from the original release.',
+        ],
+        'actions': [
+            {
+                'label': 'Open Workspace Tags',
+                'description': 'Open Personal Workspace and launch the tag-management workflow directly.',
+                'href': '/workspace?feature_action=document_tag_system',
+                'icon': 'bi-box-arrow-in-right',
+            },
+            {
+                'label': 'Read Tags Guide',
+                'description': 'Open the public release guide covering tags, grid view, and chat filtering together.',
+                'href': 'https://microsoft.github.io/simplechat/latest-release/tags-grid-view-chat-filtering/',
+                'icon': 'bi-box-arrow-up-right',
+                'is_external': True,
+                'requires_settings': [_SUPPORT_LATEST_FEATURE_DOCS_SETTING_KEY],
+            },
+        ],
+        'images': [
+            {
+                'path': 'images/features/workspace_tags.png',
+                'alt': 'Workspace tag management screenshot',
+                'title': 'Workspace Tags',
+                'caption': 'Workspace tag-management experience for creating, organizing, and reusing document tags.',
+                'label': 'Tag Management',
+            },
+        ],
+    },
+    {
+        'id': 'workspace_folder_view',
+        'title': 'Workspace Folder View',
+        'icon': 'bi-grid-3x3-gap',
+        'summary': 'Workspace documents can be viewed in a folder-style grid with tag-based drill-down, counts, search, and saved display preferences.',
+        'details': 'Workspace Folder View adds a more visual document-browsing mode for tag-heavy workspaces where users want to scan categories before opening the underlying files.',
+        'why': 'This matters because large workspaces become easier to browse when users can move between list and folder-style views depending on whether they are searching for one file or surveying a whole category.',
+        'guidance': [
+            'Switch to folder view when you want to browse by tag grouping instead of scanning a flat document table.',
+            'Use in-folder search when a tag contains many documents and you still need to narrow within that bucket.',
+            'The original release guide covers folder view together with tag workflows and chat filtering because those experiences were introduced together.',
+        ],
+        'actions': [
+            {
+                'label': 'Open Workspace Grid View',
+                'description': 'Open Personal Workspace and switch straight into the folder-style grid view.',
+                'href': '/workspace?feature_action=workspace_folder_view',
+                'icon': 'bi-box-arrow-in-right',
+            },
+            {
+                'label': 'Read Folder View Guide',
+                'description': 'Open the public release guide covering tags, folder view, and chat filtering.',
+                'href': 'https://microsoft.github.io/simplechat/latest-release/tags-grid-view-chat-filtering/',
+                'icon': 'bi-box-arrow-up-right',
+                'is_external': True,
+                'requires_settings': [_SUPPORT_LATEST_FEATURE_DOCS_SETTING_KEY],
+            },
+        ],
+        'images': [
+            {
+                'path': 'images/features/workspace_grid_view.png',
+                'alt': 'Workspace grid view screenshot',
+                'title': 'Workspace Folder Grid View',
+                'caption': 'Folder-style grid view for browsing workspace documents through tag-driven groupings.',
+                'label': 'Grid View',
+            },
+        ],
+    },
+    {
+        'id': 'multi_workspace_scope_management',
+        'title': 'Multi-Workspace Scope Management',
+        'icon': 'bi-diagram-3',
+        'summary': 'Chat can span personal, multiple group, and multiple public workspaces together, with selection freezing after the first grounded search when locking is enabled.',
+        'details': 'Multi-Workspace Scope Management expands chat scope selection so users can compose a conversation context from more than one workspace at a time before the grounded search lock takes effect.',
+        'why': 'This matters because many real workflows depend on combining evidence from multiple approved workspaces, but that needs clearer selection controls and more predictable locking behavior.',
+        'guidance': [
+            'Select the needed personal, group, and public scopes before the first grounded search if you expect to work across multiple sources.',
+            'Use the lock behavior as a signal that the conversation has now committed to the chosen evidence boundary.',
+            'Review the combined guide if you want the original walkthrough for multi-scope chat, document filters, and tag-aware narrowing.',
+        ],
+        'actions': [
+            {
+                'label': 'Open Scope Menu',
+                'description': 'Open Chat, expand grounded search, and show the multi-workspace scope picker.',
+                'href': '/chats?feature_action=multi_workspace_scope_management',
+                'icon': 'bi-box-arrow-in-right',
+            },
+            {
+                'label': 'Read Multi-Scope Guide',
+                'description': 'Open the public release guide covering multi-workspace scope management and chat filtering.',
+                'href': 'https://microsoft.github.io/simplechat/latest-release/tags-grid-view-chat-filtering/',
+                'icon': 'bi-box-arrow-up-right',
+                'is_external': True,
+                'requires_settings': [_SUPPORT_LATEST_FEATURE_DOCS_SETTING_KEY],
+            },
+        ],
+        'images': [
+            {
+                'path': 'images/features/workspace_scopes_in_chat.png',
+                'alt': 'Workspace scopes in chat screenshot',
+                'title': 'Workspace Scopes in Chat',
+                'caption': 'Chat interface showing how multiple workspace scopes can be selected together before the conversation locks.',
+                'label': 'Workspace Scopes',
+            },
+        ],
+    },
+    {
+        'id': 'chat_document_and_tag_filtering',
+        'title': 'Chat Document and Tag Filtering',
+        'icon': 'bi-funnel',
+        'summary': 'Chat filtering moved from a single-document dropdown to multi-document and multi-tag checkboxes that work across selected workspaces.',
+        'details': 'Chat Document and Tag Filtering gives users a more explicit way to narrow grounded chat context to the exact documents and tags they want included.',
+        'why': 'This matters because grounded chat gets more predictable when users can select a precise subset of source material instead of relying on one dropdown or a broad workspace search.',
+        'guidance': [
+            'Use multi-document selection when you know the exact sources that should ground the conversation.',
+            'Use multi-tag filtering when the relevant documents share a reusable label but live across several workspaces.',
+            'Open the combined release guide when you want the original walkthrough for tags, folder view, and chat filtering as one workflow.',
+        ],
+        'actions': [
+            {
+                'label': 'Open Chat Tag Filters',
+                'description': 'Open Chat, expand grounded search, and show the tag-filtering controls.',
+                'href': '/chats?feature_action=chat_document_and_tag_filtering',
+                'icon': 'bi-box-arrow-in-right',
+            },
+            {
+                'label': 'Read Filtering Guide',
+                'description': 'Open the public release guide covering chat document and tag filtering.',
+                'href': 'https://microsoft.github.io/simplechat/latest-release/tags-grid-view-chat-filtering/',
+                'icon': 'bi-box-arrow-up-right',
+                'is_external': True,
+                'requires_settings': [_SUPPORT_LATEST_FEATURE_DOCS_SETTING_KEY],
+            },
+        ],
+        'images': [
+            {
+                'path': 'images/features/chat_tags_including_doc_classification.png',
+                'alt': 'Chat tags including document classification screenshot',
+                'title': 'Chat Tag and Classification Filtering',
+                'caption': 'Chat filtering experience showing tags and document classifications together when narrowing grounded sources.',
+                'label': 'Tag and Classification Filters',
+            },
+        ],
+    },
+]
+
+_SUPPORT_LATEST_FEATURE_RELEASE_GROUPS = [
+    {
+        'id': 'current_release',
+        'label': 'Latest Features',
+        'description': 'The newest feature set your admins are currently sharing with end users.',
+        'release_version': None,
+        'default_expanded': True,
+        'collapse_id': 'supportLatestFeaturesCurrentRelease',
+        'features': _SUPPORT_LATEST_FEATURE_CATALOG,
+    },
+    {
+        'id': 'previous_release',
+        'label': 'Previous Release Features',
+        'description': 'Highlights carried forward from the earlier v0.239.001 release set so users can still find the last major round of feature announcements.',
+        'release_version': '0.239.001',
+        'default_expanded': False,
+        'collapse_id': 'supportLatestFeaturesPreviousRelease',
+        'features': _SUPPORT_PREVIOUS_RELEASE_FEATURE_CATALOG,
+    },
+]
+
+
+def _flatten_support_feature_groups(feature_groups):
+    """Return a flat list of features from grouped latest-feature metadata."""
+    flattened = []
+    for feature_group in feature_groups:
+        for feature in feature_group.get('features', []):
+            feature_copy = deepcopy(feature)
+            feature_copy['release_group_id'] = feature_group.get('id')
+            feature_copy['release_group_label'] = feature_group.get('label')
+            feature_copy['release_version'] = feature_group.get('release_version')
+            flattened.append(feature_copy)
+
+    return flattened
+
 
 def _setting_enabled(settings, key):
     """Return True when the named setting is enabled."""
@@ -608,12 +937,20 @@ def _normalize_feature_media(feature):
 
 def get_support_latest_feature_catalog():
     """Return a copy of the support latest-features catalog."""
-    return deepcopy(_SUPPORT_LATEST_FEATURE_CATALOG)
+    return _flatten_support_feature_groups(_SUPPORT_LATEST_FEATURE_RELEASE_GROUPS)
+
+
+def get_support_latest_feature_release_groups():
+    """Return grouped latest-feature metadata organized by release."""
+    return deepcopy(_SUPPORT_LATEST_FEATURE_RELEASE_GROUPS)
 
 
 def get_default_support_latest_features_visibility():
     """Return default visibility for each user-facing latest feature."""
-    defaults = {item['id']: True for item in _SUPPORT_LATEST_FEATURE_CATALOG}
+    defaults = {
+        item['id']: True
+        for item in _flatten_support_feature_groups(_SUPPORT_LATEST_FEATURE_RELEASE_GROUPS)
+    }
     defaults['deployment'] = False
     defaults['redis_key_vault'] = False
     return defaults
@@ -653,6 +990,50 @@ def get_visible_support_latest_features(settings):
     return visible_items
 
 
+def get_visible_support_latest_feature_groups(settings):
+    """Return visible latest-feature entries grouped by release metadata."""
+    normalized_visibility = normalize_support_latest_features_visibility(
+        (settings or {}).get('support_latest_features_visibility', {})
+    )
+    visible_groups = []
+
+    for feature_group in _SUPPORT_LATEST_FEATURE_RELEASE_GROUPS:
+        visible_features = []
+        for feature in feature_group.get('features', []):
+            if not normalized_visibility.get(feature['id'], True):
+                continue
+
+            visible_feature = deepcopy(feature)
+            visible_feature['actions'] = [
+                action for action in visible_feature.get('actions', [])
+                if _action_enabled(action, settings)
+            ]
+            _normalize_feature_media(visible_feature)
+            visible_features.append(visible_feature)
+
+        if visible_features:
+            visible_group = deepcopy(feature_group)
+            visible_group['features'] = visible_features
+            visible_groups.append(visible_group)
+
+    return visible_groups
+
+
+def get_support_latest_feature_release_groups_for_settings(settings):
+    """Return grouped latest-feature metadata with actions filtered for the current settings."""
+    filtered_groups = deepcopy(_SUPPORT_LATEST_FEATURE_RELEASE_GROUPS)
+
+    for feature_group in filtered_groups:
+        for feature in feature_group.get('features', []):
+            feature['actions'] = [
+                action for action in feature.get('actions', [])
+                if _action_enabled(action, settings)
+            ]
+            _normalize_feature_media(feature)
+
+    return filtered_groups
+
+
 def has_visible_support_latest_features(settings):
     """Return True when at least one latest-feature entry is enabled for users."""
     normalized_visibility = normalize_support_latest_features_visibility(
diff --git a/application/single_app/templates/_sidebar_nav.html b/application/single_app/templates/_sidebar_nav.html
index d53586cf..0c106e39 100644
--- a/application/single_app/templates/_sidebar_nav.html
+++ b/application/single_app/templates/_sidebar_nav.html
@@ -350,6 +350,11 @@
                   <i class="bi bi-life-preserver me-2" style="font-size: 0.8em;"></i><span class="nav-text">Support Menu</span>
                 </a>
               </li>
+              <li class="nav-item">
+                <a class="nav-link d-flex align-items-center admin-nav-section" href="#" data-tab="latest-features" data-section="latest-features-previous-release-card">
+                  <i class="bi bi-clock-history me-2" style="font-size: 0.8em;"></i><span class="nav-text">Previous Release</span>
+                </a>
+              </li>
             </ul>
           </li>
           <li class="nav-item">
diff --git a/application/single_app/templates/admin_settings.html b/application/single_app/templates/admin_settings.html
index c43d6820..1171ce97 100644
--- a/application/single_app/templates/admin_settings.html
+++ b/application/single_app/templates/admin_settings.html
@@ -1693,20 +1693,56 @@ <h5>
                         <div id="support_latest_features_settings" {% if not settings.enable_support_latest_features %}style="display: none;"{% endif %}>
                             <h6 class="mt-3">User-Facing Latest Features</h6>
                             <p class="text-muted small">Choose which recent features are shared on the user Latest Features page. Deployment and Redis start unchecked because they are mainly admin-facing rollout and infrastructure topics.</p>
-                            <div class="row g-2">
-                                {% for feature in support_latest_feature_catalog %}
-                                <div class="col-md-6">
-                                    <div class="form-check border rounded p-3 h-100">
-                                        <input class="form-check-input" type="checkbox" id="support_latest_feature_{{ feature.id }}" name="support_latest_feature_{{ feature.id }}"
-                                            {% if settings.support_latest_features_visibility.get(feature.id, true) %}checked{% endif %}>
-                                        <label class="form-check-label ms-2" for="support_latest_feature_{{ feature.id }}">
-                                            <span class="fw-semibold d-block">{{ feature.title }}</span>
-                                            <span class="text-muted small">{{ feature.summary }}</span>
-                                        </label>
+                            <div class="form-check form-switch mb-3">
+                                <input class="form-check-input" type="checkbox" id="enable_support_latest_feature_documentation_links" name="enable_support_latest_feature_documentation_links"
+                                    {% if settings.enable_support_latest_feature_documentation_links %}checked{% endif %}>
+                                <label class="form-check-label ms-2" for="enable_support_latest_feature_documentation_links">
+                                    Show Simple Chat Documentation Guide Links
+                                </label>
+                                <i class="bi bi-info-circle ms-2" data-bs-toggle="tooltip" title="Show public documentation guide buttons alongside the in-app Latest Features shortcuts. This is disabled by default."></i>
+                                <small class="form-text text-muted d-block mt-1">When enabled, user-facing Latest Features cards can show public guide buttons in addition to the direct in-app shortcuts.</small>
+                            </div>
+                            {% for release_group in support_latest_feature_release_groups %}
+                            {% set checklist_collapse_id = release_group.collapse_id ~ 'Checklist' %}
+                            <div class="card border-0 bg-body-tertiary mb-3">
+                                <div class="card-body p-3">
+                                    <div class="d-flex flex-column flex-md-row align-items-md-center justify-content-between gap-3">
+                                        <div>
+                                            <h6 class="mb-1">{{ release_group.label }}{% if release_group.release_version %}<span class="badge bg-light text-dark ms-2">v{{ release_group.release_version }}</span>{% endif %}</h6>
+                                            <p class="text-muted small mb-0">{{ release_group.description }}</p>
+                                        </div>
+                                        {% if not release_group.default_expanded %}
+                                        <button
+                                            type="button"
+                                            class="btn btn-sm btn-outline-secondary"
+                                            data-bs-toggle="collapse"
+                                            data-bs-target="#{{ checklist_collapse_id }}"
+                                            aria-expanded="false"
+                                            aria-controls="{{ checklist_collapse_id }}"
+                                        >
+                                            Show {{ release_group.label }}
+                                        </button>
+                                        {% endif %}
+                                    </div>
+                                    <div {% if not release_group.default_expanded %}class="collapse mt-3" id="{{ checklist_collapse_id }}"{% else %}class="mt-3"{% endif %}>
+                                        <div class="row g-2">
+                                            {% for feature in release_group.features %}
+                                            <div class="col-md-6">
+                                                <div class="form-check border rounded p-3 h-100">
+                                                    <input class="form-check-input" type="checkbox" id="support_latest_feature_{{ feature.id }}" name="support_latest_feature_{{ feature.id }}"
+                                                        {% if settings.support_latest_features_visibility.get(feature.id, true) %}checked{% endif %}>
+                                                    <label class="form-check-label ms-2" for="support_latest_feature_{{ feature.id }}">
+                                                        <span class="fw-semibold d-block">{{ feature.title }}</span>
+                                                        <span class="text-muted small">{{ feature.summary }}</span>
+                                                    </label>
+                                                </div>
+                                            </div>
+                                            {% endfor %}
+                                        </div>
                                     </div>
                                 </div>
-                                {% endfor %}
                             </div>
+                            {% endfor %}
                         </div>
                     </div>
                 </div>
@@ -2847,6 +2883,93 @@ <h5 class="mb-1">
                         </div>
                     </div>
                 </div>
+
+                {% for release_group in support_latest_feature_release_groups_preview %}
+                {% if release_group.id == 'previous_release' %}
+                <div class="card p-3 mb-3 latest-feature-card" id="latest-features-previous-release-card">
+                    <div class="latest-feature-header">
+                        <div class="latest-feature-copy">
+                            <h5 class="mb-1">
+                                <i class="bi bi-clock-history me-2"></i>{{ release_group.label }}
+                            </h5>
+                            <p class="text-muted mb-0">{{ release_group.description }}</p>
+                        </div>
+                        <a href="#latestFeaturesPreviousRelease" class="fw-bold latest-feature-toggle" data-bs-toggle="collapse" aria-expanded="false" aria-controls="latestFeaturesPreviousRelease">
+                            Show Details
+                        </a>
+                    </div>
+                    <div class="collapse mt-3" id="latestFeaturesPreviousRelease">
+                        <div class="card card-body">
+                            <div class="alert alert-secondary mb-3" role="alert">
+                                These were the headline user-facing items in the earlier v{{ release_group.release_version }} release set. Keeping them here gives admins a simple N and N-1 view without mixing older items into the current release list.
+                            </div>
+                            <div class="row g-3">
+                                {% for feature in release_group.features %}
+                                <div class="col-xl-6">
+                                    <div class="border rounded p-3 h-100 bg-body-tertiary">
+                                        <div class="d-flex flex-column gap-3 h-100">
+                                            <div class="d-flex align-items-start justify-content-between gap-3">
+                                                <div>
+                                                    <h6 class="mb-1"><i class="bi {{ feature.icon }} me-2"></i>{{ feature.title }}</h6>
+                                                    <p class="text-muted small mb-0">{{ feature.summary }}</p>
+                                                </div>
+                                                <span class="badge {% if settings.support_latest_features_visibility.get(feature.id, true) %}bg-success{% else %}bg-secondary{% endif %}">
+                                                    {% if settings.support_latest_features_visibility.get(feature.id, true) %}Shared with Users{% else %}Hidden from Users{% endif %}
+                                                </span>
+                                            </div>
+                                            <p class="small mb-0">{{ feature.details }}</p>
+                                            {% if feature.guidance %}
+                                            <ul class="small mb-0">
+                                                {% for tip in feature.guidance %}
+                                                <li>{{ tip }}</li>
+                                                {% endfor %}
+                                            </ul>
+                                            {% endif %}
+                                            {% if feature.images %}
+                                            <div class="latest-feature-gallery">
+                                                {% for image in feature.images %}
+                                                <button
+                                                    type="button"
+                                                    class="latest-feature-thumbnail-trigger"
+                                                    data-latest-feature-image-src="{{ url_for('static', filename=image.path) }}"
+                                                    data-latest-feature-image-title="{{ image.title }}"
+                                                    data-latest-feature-image-caption="{{ image.caption }}"
+                                                >
+                                                    <div class="latest-feature-thumbnail-card h-100">
+                                                        <img class="latest-feature-thumbnail-image" src="{{ url_for('static', filename=image.path) }}" alt="{{ image.alt }}">
+                                                        <div class="latest-feature-thumbnail-body">
+                                                            <div class="latest-feature-thumbnail-title">{{ image.label }}</div>
+                                                            <div class="latest-feature-thumbnail-meta">Click to enlarge</div>
+                                                        </div>
+                                                    </div>
+                                                </button>
+                                                {% endfor %}
+                                            </div>
+                                            {% endif %}
+                                            {% if feature.actions %}
+                                            <div class="d-flex flex-wrap gap-2 mt-auto pt-2">
+                                                {% for action in feature.actions %}
+                                                <a
+                                                    class="btn btn-outline-primary btn-sm"
+                                                    href="{% if action.href %}{{ action.href }}{% else %}{{ url_for(action.endpoint) }}{% if action.fragment %}#{{ action.fragment }}{% endif %}{% endif %}"
+                                                    {% if action.is_external %}target="_blank" rel="noopener noreferrer"{% endif %}
+                                                >
+                                                    <i class="bi {{ action.icon }} me-1"></i>{{ action.label }}
+                                                </a>
+                                                {% endfor %}
+                                            </div>
+                                            {% endif %}
+                                        </div>
+                                    </div>
+                                </div>
+                                {% endfor %}
+                            </div>
+                            <p class="text-muted small mb-0 mt-3">Visibility still comes from <strong>General &gt; User-Facing Latest Features</strong>, so admins can keep previous release content available without promoting every item forever.</p>
+                        </div>
+                    </div>
+                </div>
+                {% endif %}
+                {% endfor %}
             </div>
 
             
diff --git a/application/single_app/templates/group_workspaces.html b/application/single_app/templates/group_workspaces.html
index 771649df..60ba2a5c 100644
--- a/application/single_app/templates/group_workspaces.html
+++ b/application/single_app/templates/group_workspaces.html
@@ -1318,6 +1318,29 @@ <h6>Currently Shared With:</h6>
     </form>
   </div>
 </div>
+
+<!-- Group Document Delete Modal -->
+<div class="modal fade" id="groupDocumentDeleteModal" tabindex="-1" aria-labelledby="groupDocumentDeleteModalLabel" aria-hidden="true" autocomplete="off" data-lpignore="true" data-1p-ignore="true" data-bwignore="true">
+  <div class="modal-dialog">
+    <div class="modal-content">
+      <div class="modal-header">
+        <h5 class="modal-title" id="groupDocumentDeleteModalLabel">Delete Group Document</h5>
+        <button type="button" class="btn-close" data-bs-dismiss="modal" aria-label="Close"></button>
+      </div>
+      <div class="modal-body" id="groupDocumentDeleteModalBody">
+        <p class="mb-0">Choose how you want to delete this group document revision.</p>
+      </div>
+      <div class="modal-footer d-flex flex-wrap justify-content-between gap-2">
+        <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Cancel</button>
+        <div class="d-flex flex-wrap gap-2">
+          <button type="button" class="btn btn-outline-danger" id="groupDeleteCurrentBtn">Delete Current Version</button>
+          <button type="button" class="btn btn-danger" id="groupDeleteAllBtn">Delete All Versions</button>
+        </div>
+      </div>
+    </div>
+  </div>
+</div>
+
 <!-- Bulk Tag Assignment Modal (Group) -->
 <div class="modal fade" id="groupBulkTagModal" tabindex="-1" aria-labelledby="groupBulkTagModalLabel" aria-hidden="true" autocomplete="off" data-lpignore="true" data-1p-ignore="true" data-bwignore="true">
   <div class="modal-dialog modal-lg">
@@ -2611,27 +2634,6 @@ <h5 class="modal-title" id="groupTagSelectionModalLabel">Select Tags</h5>
               </ul>
             </div>
           </div>
-
-          <div class="modal fade" id="groupDocumentDeleteModal" tabindex="-1" aria-labelledby="groupDocumentDeleteModalLabel" aria-hidden="true" autocomplete="off" data-lpignore="true" data-1p-ignore="true" data-bwignore="true">
-            <div class="modal-dialog">
-              <div class="modal-content">
-                <div class="modal-header">
-                  <h5 class="modal-title" id="groupDocumentDeleteModalLabel">Delete Group Document</h5>
-                  <button type="button" class="btn-close" data-bs-dismiss="modal" aria-label="Close"></button>
-                </div>
-                <div class="modal-body" id="groupDocumentDeleteModalBody">
-                  <p class="mb-0">Choose how you want to delete this group document revision.</p>
-                </div>
-                <div class="modal-footer d-flex flex-wrap justify-content-between gap-2">
-                  <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Cancel</button>
-                  <div class="d-flex flex-wrap gap-2">
-                    <button type="button" class="btn btn-outline-danger" id="groupDeleteCurrentBtn">Delete Current Version</button>
-                    <button type="button" class="btn btn-danger" id="groupDeleteAllBtn">Delete All Versions</button>
-                  </div>
-                </div>
-              </div>
-            </div>
-          </div>
         `;
       }
     }
diff --git a/application/single_app/templates/latest_features.html b/application/single_app/templates/latest_features.html
index ebea3fe4..1b16c396 100644
--- a/application/single_app/templates/latest_features.html
+++ b/application/single_app/templates/latest_features.html
@@ -160,6 +160,34 @@
     padding-top: 0.9rem;
   }
 
+  .support-feature-release-panel {
+    border: 1px solid rgba(0, 0, 0, 0.08);
+    border-radius: 1rem;
+    margin-top: 1.5rem;
+    padding: 1rem 1rem 1.1rem;
+  }
+
+  .support-feature-release-heading {
+    align-items: center;
+    display: flex;
+    gap: 1rem;
+    justify-content: space-between;
+  }
+
+  .support-feature-release-toggle {
+    flex-shrink: 0;
+  }
+
+  .support-feature-release-version {
+    color: #6c757d;
+    font-size: 0.9rem;
+    margin-top: 0.25rem;
+  }
+
+  .support-feature-release-body {
+    margin-top: 1rem;
+  }
+
   .support-feature-icon {
     width: 2.5rem;
     height: 2.5rem;
@@ -258,10 +286,124 @@
   [data-bs-theme="dark"] .support-feature-passive-note {
     color: rgba(226, 232, 240, 0.8);
   }
+
+  [data-bs-theme="dark"] .support-feature-release-panel {
+    border-color: rgba(148, 163, 184, 0.18);
+  }
+
+  @media (max-width: 767.98px) {
+    .support-feature-release-heading {
+      align-items: stretch;
+      flex-direction: column;
+    }
+
+    .support-feature-release-toggle {
+      width: 100%;
+    }
+  }
 </style>
 {% endblock %}
 
 {% block content %}
+{% macro render_support_feature_card(feature) %}
+<div class="col-12">
+  <div class="card support-feature-card shadow-sm h-100">
+    <div class="card-body p-4">
+      <div class="d-flex flex-column flex-xl-row gap-4 align-items-start">
+        {% if feature.images %}
+        <div class="support-feature-gallery">
+          {% for image in feature.images %}
+          <button
+            type="button"
+            class="support-feature-thumbnail-trigger"
+            data-latest-feature-image-src="{{ url_for('static', filename=image.path) }}"
+            data-latest-feature-image-title="{{ image.title }}"
+            data-latest-feature-image-caption="{{ image.caption }}"
+            aria-label="View {{ image.title }} image"
+          >
+            <span class="support-feature-thumbnail-card">
+              <img class="support-feature-media" src="{{ url_for('static', filename=image.path) }}" alt="{{ image.alt }}" />
+              <span class="support-feature-thumbnail-title">{{ image.label }}</span>
+              <span class="support-feature-thumbnail-meta">Click to enlarge</span>
+            </span>
+          </button>
+          {% endfor %}
+        </div>
+        {% elif feature.image %}
+        <button
+          type="button"
+          class="support-feature-thumbnail-trigger"
+          data-latest-feature-image-src="{{ url_for('static', filename=feature.image) }}"
+          data-latest-feature-image-title="{{ feature.title }}"
+          data-latest-feature-image-caption="{{ feature.summary }}"
+          aria-label="View {{ feature.title }} image"
+        >
+          <span class="support-feature-thumbnail-card">
+            <img class="support-feature-media" src="{{ url_for('static', filename=feature.image) }}" alt="{{ feature.image_alt }}" />
+            <span class="support-feature-thumbnail-title">{{ feature.title }}</span>
+            <span class="support-feature-thumbnail-meta">Click to enlarge</span>
+          </span>
+        </button>
+        {% endif %}
+        <div class="flex-grow-1 support-feature-copy-block">
+          <div class="d-flex align-items-center gap-3 mb-3">
+            <span class="support-feature-icon">
+              <i class="bi {{ feature.icon }}"></i>
+            </span>
+            <div>
+              <h4 class="mb-1">{{ feature.title }}</h4>
+              <p class="text-muted mb-0">{{ feature.summary }}</p>
+            </div>
+          </div>
+          <p class="mb-0">{{ feature.details }}</p>
+
+          <div class="support-feature-sections">
+            <div class="support-feature-callout">
+              <div class="support-feature-section-title">Why It Matters</div>
+              <p class="mb-0">{{ feature.why }}</p>
+            </div>
+
+            {% if feature.guidance %}
+            <div>
+              <div class="support-feature-section-title">How To Try It</div>
+              <ul class="support-feature-guidance-list">
+                {% for tip in feature.guidance %}
+                <li>{{ tip }}</li>
+                {% endfor %}
+              </ul>
+            </div>
+            {% endif %}
+
+            {% if feature.actions %}
+            <div>
+              <div class="support-feature-section-title">Open The Right Page</div>
+              <div class="support-feature-action-grid">
+                {% for action in feature.actions %}
+                <a
+                  class="support-feature-action-card"
+                  href="{% if action.href %}{{ action.href }}{% else %}{{ url_for(action.endpoint) }}{% if action.fragment %}#{{ action.fragment }}{% endif %}{% endif %}"
+                  {% if action.is_external %}target="_blank" rel="noopener noreferrer"{% endif %}
+                >
+                  <span class="support-feature-action-label"><i class="bi {{ action.icon }} me-2"></i>{{ action.label }}</span>
+                  <span class="support-feature-action-description">{{ action.description }}</span>
+                </a>
+                {% endfor %}
+              </div>
+            </div>
+            {% if feature.id == 'guided_tutorials' %}
+            <p class="support-feature-passive-note mb-0">Guided tutorial buttons are shown by default. If you want them out of the way after onboarding, use the profile shortcut above to hide or restore them for your own account.</p>
+            {% endif %}
+            {% else %}
+            <p class="support-feature-passive-note mb-0">{{ feature.passive_note or 'This is mostly a behind-the-scenes improvement managed by your admins. You will usually notice it through a smoother experience rather than a new user control.' }}</p>
+            {% endif %}
+          </div>
+        </div>
+      </div>
+    </div>
+  </div>
+</div>
+{% endmacro %}
+
 <div class="container py-4">
   <div class="d-flex flex-column flex-lg-row align-items-lg-center justify-content-between gap-3 mb-4">
     <div>
@@ -271,106 +413,45 @@ <h2 class="mb-1">Latest Features</h2>
     <span class="badge bg-warning text-dark text-uppercase align-self-start align-self-lg-center">New</span>
   </div>
 
+  {% if support_latest_features or support_previous_release_feature_groups %}
   {% if support_latest_features %}
   <div class="row g-3">
     {% for feature in support_latest_features %}
-    <div class="col-12">
-      <div class="card support-feature-card shadow-sm h-100">
-        <div class="card-body p-4">
-          <div class="d-flex flex-column flex-xl-row gap-4 align-items-start">
-            {% if feature.images %}
-            <div class="support-feature-gallery">
-              {% for image in feature.images %}
-              <button
-                type="button"
-                class="support-feature-thumbnail-trigger"
-                data-latest-feature-image-src="{{ url_for('static', filename=image.path) }}"
-                data-latest-feature-image-title="{{ image.title }}"
-                data-latest-feature-image-caption="{{ image.caption }}"
-                aria-label="View {{ image.title }} image"
-              >
-                <span class="support-feature-thumbnail-card">
-                  <img class="support-feature-media" src="{{ url_for('static', filename=image.path) }}" alt="{{ image.alt }}" />
-                  <span class="support-feature-thumbnail-title">{{ image.label }}</span>
-                  <span class="support-feature-thumbnail-meta">Click to enlarge</span>
-                </span>
-              </button>
-              {% endfor %}
-            </div>
-            {% elif feature.image %}
-            <button
-              type="button"
-              class="support-feature-thumbnail-trigger"
-              data-latest-feature-image-src="{{ url_for('static', filename=feature.image) }}"
-              data-latest-feature-image-title="{{ feature.title }}"
-              data-latest-feature-image-caption="{{ feature.summary }}"
-              aria-label="View {{ feature.title }} image"
-            >
-              <span class="support-feature-thumbnail-card">
-                <img class="support-feature-media" src="{{ url_for('static', filename=feature.image) }}" alt="{{ feature.image_alt }}" />
-                <span class="support-feature-thumbnail-title">{{ feature.title }}</span>
-                <span class="support-feature-thumbnail-meta">Click to enlarge</span>
-              </span>
-            </button>
-            {% endif %}
-            <div class="flex-grow-1 support-feature-copy-block">
-              <div class="d-flex align-items-center gap-3 mb-3">
-                <span class="support-feature-icon">
-                  <i class="bi {{ feature.icon }}"></i>
-                </span>
-                <div>
-                  <h4 class="mb-1">{{ feature.title }}</h4>
-                  <p class="text-muted mb-0">{{ feature.summary }}</p>
-                </div>
-              </div>
-              <p class="mb-0">{{ feature.details }}</p>
-
-              <div class="support-feature-sections">
-                <div class="support-feature-callout">
-                  <div class="support-feature-section-title">Why It Matters</div>
-                  <p class="mb-0">{{ feature.why }}</p>
-                </div>
-
-                {% if feature.guidance %}
-                <div>
-                  <div class="support-feature-section-title">How To Try It</div>
-                  <ul class="support-feature-guidance-list">
-                    {% for tip in feature.guidance %}
-                    <li>{{ tip }}</li>
-                    {% endfor %}
-                  </ul>
-                </div>
-                {% endif %}
-
-                {% if feature.actions %}
-                <div>
-                  <div class="support-feature-section-title">Open The Right Page</div>
-                  <div class="support-feature-action-grid">
-                    {% for action in feature.actions %}
-                    <a
-                      class="support-feature-action-card"
-                      href="{{ url_for(action.endpoint) }}{% if action.fragment %}#{{ action.fragment }}{% endif %}"
-                    >
-                      <span class="support-feature-action-label"><i class="bi {{ action.icon }} me-2"></i>{{ action.label }}</span>
-                      <span class="support-feature-action-description">{{ action.description }}</span>
-                    </a>
-                    {% endfor %}
-                  </div>
-                </div>
-                {% if feature.id == 'guided_tutorials' %}
-                <p class="support-feature-passive-note mb-0">Guided tutorial buttons are shown by default. If you want them out of the way after onboarding, use the profile shortcut above to hide or restore them for your own account.</p>
-                {% endif %}
-                {% else %}
-                <p class="support-feature-passive-note mb-0">This is mostly a behind-the-scenes improvement managed by your admins. You will usually notice it through a smoother experience rather than a new user control.</p>
-                {% endif %}
-              </div>
-            </div>
-          </div>
-        </div>
-      </div>
-    </div>
+    {{ render_support_feature_card(feature) }}
     {% endfor %}
   </div>
+  {% endif %}
+
+  {% for release_group in support_previous_release_feature_groups %}
+  <section class="support-feature-release-panel" aria-labelledby="{{ release_group.collapse_id }}Heading">
+    <div class="support-feature-release-heading">
+      <div>
+        <h3 class="h5 mb-1" id="{{ release_group.collapse_id }}Heading">{{ release_group.label }}</h3>
+        <p class="text-muted mb-0">{{ release_group.description }}</p>
+        {% if release_group.release_version %}
+        <div class="support-feature-release-version">Based on the v{{ release_group.release_version }} release.</div>
+        {% endif %}
+      </div>
+      <button
+        type="button"
+        class="btn btn-outline-secondary support-feature-release-toggle"
+        data-bs-toggle="collapse"
+        data-bs-target="#{{ release_group.collapse_id }}"
+        aria-expanded="false"
+        aria-controls="{{ release_group.collapse_id }}"
+      >
+        Show {{ release_group.label }}
+      </button>
+    </div>
+    <div class="collapse support-feature-release-body" id="{{ release_group.collapse_id }}">
+      <div class="row g-3">
+        {% for feature in release_group.features %}
+        {{ render_support_feature_card(feature) }}
+        {% endfor %}
+      </div>
+    </div>
+  </section>
+  {% endfor %}
   {% else %}
   <div class="alert alert-info" role="alert">
     Your admins have not shared any Latest Features announcements right now.
diff --git a/application/single_app/templates/profile.html b/application/single_app/templates/profile.html
index 061eec3c..685315e7 100644
--- a/application/single_app/templates/profile.html
+++ b/application/single_app/templates/profile.html
@@ -454,7 +454,7 @@ <h5 class="mb-2"><i class="bi bi-journal-text me-2"></i>Fact Memory</h5>
 
     <!-- Retention Policy Settings -->
     {% if app_settings.enable_retention_policy_personal %}
-    <div class="section-card">
+    <div class="section-card" id="retention-policy-settings">
         <h5 class="mb-3"><i class="bi bi-hourglass-split me-2"></i>Retention Policy Settings</h5>
         <p class="text-muted">Configure how long to keep your conversations and documents. Items older than the specified period will be automatically deleted.</p>
         
@@ -907,6 +907,31 @@ <h5 class="modal-title" id="exportActivityModalLabel">
     }
 }
 
+function handleProfileFeatureAction() {
+    const url = new URL(window.location.href);
+    const featureAction = url.searchParams.get('feature_action') || '';
+
+    if (featureAction !== 'retention_policy') {
+        return;
+    }
+
+    const retentionSection = document.getElementById('retention-policy-settings');
+    const retentionSelect = document.getElementById('conversation_retention_days');
+
+    if (retentionSection) {
+        retentionSection.scrollIntoView({ behavior: 'smooth', block: 'start' });
+    }
+
+    if (retentionSelect) {
+        window.setTimeout(() => {
+            retentionSelect.focus({ preventScroll: true });
+        }, 150);
+    }
+
+    url.searchParams.delete('feature_action');
+    window.history.replaceState({}, document.title, `${url.pathname}${url.search}${url.hash}`);
+}
+
 document.addEventListener('DOMContentLoaded', function() {
     console.log('Profile DOMContentLoaded fired');
     
@@ -923,6 +948,7 @@ <h5 class="modal-title" id="exportActivityModalLabel">
     }
     
     loadRetentionSettings();
+    handleProfileFeatureAction();
     loadTutorialPreferences();
     loadFactMemory();
     loadMicrophoneSettings();
diff --git a/docs/explanation/features/v0.241.001/LATEST_FEATURES_ACTION_LINKS.md b/docs/explanation/features/v0.241.001/LATEST_FEATURES_ACTION_LINKS.md
new file mode 100644
index 00000000..c5c2ae3b
--- /dev/null
+++ b/docs/explanation/features/v0.241.001/LATEST_FEATURES_ACTION_LINKS.md
@@ -0,0 +1,61 @@
+# Latest Features Action Links (v0.241.003)
+
+## Overview
+This update turns the earlier Previous Release feature cards into direct in-app entry points. Users can now jump from Support > Latest Features into the matching Chat, Workspace, and Profile workflows instead of stopping at a descriptive card.
+
+Version Updated: 0.241.003
+
+## Dependencies
+- `application/single_app/support_menu_config.py`
+- `application/single_app/functions_settings.py`
+- `application/single_app/route_frontend_admin_settings.py`
+- `application/single_app/templates/admin_settings.html`
+- `application/single_app/static/js/chat/chat-onload.js`
+- `application/single_app/static/js/chat/chat-documents.js`
+- `application/single_app/static/js/workspace/workspace-init.js`
+- `application/single_app/static/js/workspace/workspace-tags.js`
+- `application/single_app/templates/profile.html`
+- `functional_tests/test_latest_features_action_links.py`
+- `ui_tests/test_latest_features_action_launchers.py`
+
+## Implemented in version: **0.241.003**
+
+## Technical Specifications
+
+### Action Metadata
+- Previous-release Latest Features cards now include direct in-app buttons for:
+  - conversation export
+  - retention settings
+  - workspace tag management
+  - workspace grid view
+  - chat scope management
+  - chat tag filtering
+- Public documentation guide buttons remain available through the same feature metadata, but they are now conditional.
+
+### Admin-Controlled Guide Links
+- A new General settings toggle named **Show Simple Chat Documentation Guide Links** controls whether public documentation buttons are shown on Latest Features cards.
+- The setting defaults to `False` so users see only the in-app shortcuts unless an admin explicitly enables the external guide links.
+- Admin preview cards use the same filtered action list, so the admin tab reflects what end users will actually see.
+
+### Launch Intents
+- Chat launch intents use the `feature_action` query parameter to:
+  - open the first available conversation export workflow
+  - open the multi-workspace scope selector
+  - open the chat tag-filter controls
+- Workspace launch intents use the same parameter to:
+  - open the tag-management modal
+  - switch directly into grid view
+- Profile launch intents jump to the retention settings section and focus the retention control.
+
+## Usage Instructions
+- Open **Support > Latest Features** and expand **Previous Release Features**.
+- Choose an in-app action button when you want to land directly in the related workflow.
+- Open **Admin Settings > General > User-Facing Latest Features** when you want to enable or disable the public documentation guide buttons.
+
+## Testing and Validation
+- Confirm the new admin toggle is saved and restored correctly.
+- Confirm previous-release cards still show their in-app action buttons when guide links are disabled.
+- Confirm guide buttons appear only when the new admin toggle is enabled.
+- Confirm workspace launch links open grid view or tag management directly.
+- Confirm the profile launch link scrolls to retention settings.
+- Confirm the chat launch links open grounded-search scope controls or the export workflow as expected.
\ No newline at end of file
diff --git a/docs/explanation/features/v0.241.001/LATEST_FEATURES_ADMIN_TAB.md b/docs/explanation/features/v0.241.001/LATEST_FEATURES_ADMIN_TAB.md
index 01661033..3bdf120f 100644
--- a/docs/explanation/features/v0.241.001/LATEST_FEATURES_ADMIN_TAB.md
+++ b/docs/explanation/features/v0.241.001/LATEST_FEATURES_ADMIN_TAB.md
@@ -1,130 +1,55 @@
-# Latest Features Admin Tab (v0.240.085)
+# Latest Features Release Grouping (v0.241.002)
 
 ## Overview
-This feature adds a dedicated **Latest Features** tab to Admin Settings so administrators can review the most important recent capabilities in one place and decide what to communicate to users.
+This update extends the existing **Latest Features** experience so admins and end users can see both the current release highlights and the immediately previous release highlights without merging them into one long list.
 
-Version Updated: 0.240.085
+Version Updated: 0.241.002
 
 ## Dependencies
-- `application/single_app/templates/admin_settings.html`
-- `application/single_app/static/js/admin/admin_settings.js`
-- `application/single_app/functions_settings.py`
+- `application/single_app/support_menu_config.py`
+- `application/single_app/route_frontend_support.py`
 - `application/single_app/route_frontend_admin_settings.py`
+- `application/single_app/templates/latest_features.html`
+- `application/single_app/templates/admin_settings.html`
+- `application/single_app/templates/_sidebar_nav.html`
 
-## Implemented in version: **0.240.003**
+## Implemented in version: **0.241.002**
 
 ## Technical Specifications
 
-### Admin Settings Placement
-- The tab is added directly to the existing Admin Settings tab list.
-- It is positioned near the front of the page so administrators can review new functionality early.
-- Content is grouped into collapsible cards to keep the page readable even as additional features are added in future releases.
-
-### Feature Grouping
-The tab groups recent functionality into broader themes instead of listing every release note entry separately:
-- Release Notifications Registration
-- Guided Tutorials
-- Background Chat Completion
-- Multi-Endpoint GPT Selection
-- Tabular Data Analysis
-- Citation Improvements
-- Document Revisioning and Management
-- Conversation Summaries and Export
-- Agent and Action Operations
-- AI Transparency
-- Fact Memory
-- Deployment and Runtime Guidance
-- Redis and Key Vault
-- Send Feedback
-- Support Menu
-
-### Mirrored Settings
-Two high-impact configuration areas are mirrored in the Latest Features tab:
-- `enable_thoughts`
-- Enhanced Citations settings:
-  - `enable_enhanced_citations`
-  - `office_docs_authentication_type`
-  - `office_docs_storage_account_url`
-  - `office_docs_storage_account_blob_endpoint`
-  - `tabular_preview_max_blob_size_mb`
-- Redis cache settings:
-  - `enable_redis_cache`
-  - `redis_url`
-  - `redis_auth_type`
-  - `redis_key`
-
-The mirrored controls are UI proxies only. They do not create new saved settings. JavaScript keeps them synchronized with the canonical controls in the existing tabs.
-
-### Screenshot Gallery Strategy
-Saved screenshots are rendered directly from:
-- `application/single_app/static/images/features/`
-
-Current screenshots surfaced in the admin UI:
-- `guided_tutorials_chat.png`
-- `guided_tutorials_workspace.png`
-- `background_completion_notifications-01.png`
-- `background_completion_notifications-02.png`
-- `model_selection_multi_endpoint_admin.png`
-- `agent_default_model_review_summary.png`
-- `agent_default_model_review_action.png`
-- `tabular_analysis_enhanced_citations.png`
-- `citation_improvements_history_replay.png`
-- `citation_improvements_amplified_results.png`
-- `document_revision_workspace.png`
-- `document_revision_delete_compare.png`
-- `enable_support_menu_for_end_users.png`
-- `conversation_summary_card.png`
-- `pdf_export_option.png`
-- `per_message_export_menu.png`
-- `agent_action_grid_view.png`
-- `sql_test_connection.png`
-- `thoughts_visibility.png`
-- `facts_memory_view_profile.png`
-- `fact_memory_management.png`
-- `facts_citation_and_thoughts.png`
-- `gunicorn_startup_guidance.png`
-- `redis_key_vault.png`
-- `support_menu_entry.png`
-
-Each screenshot now renders as a thumbnail in the Latest Features tab. Clicking a thumbnail opens a larger popup modal with a close button, and clicking outside the popup also dismisses it. The popup styling is tuned for both light and dark themes so the caption text, framed image surface, and modal shell remain easy to distinguish.
-
-The GPT selection, citation improvement, document revision, and Support Menu entries now use saved PNG screenshots so the admin preview matches the current product surfaces more closely.
-
-The release notifications registration explainer is intentionally text-only. It points admins to a live control that already exists at the top of Admin Settings, so no duplicate screenshot is needed.
-
-### New Feature Coverage
-- **Release Notifications Registration** explains the Registered or Unregistered badge beside the version number, clarifies that it is admin-only, and tells admins that clicking it opens the modal used to register this environment for release updates.
-- **Multi-Endpoint GPT Selection** highlights the admin workflow for enabling multiple model endpoints, configuring the default fallback model used when a request does not provide an explicit selection, and using the admin-only Agent Default Model Review modal to selectively rebind inherited or explicitly overridden agents.
-- **Citation Improvements** explains conversation history citation replay and citation amplification so admins understand why follow-up questions stay grounded even when the assistant is working from prior evidence.
-- **Document Revisioning and Management** explains that same-name uploads create versioned revision families, keep previous versions available for traceability, and carry classifications and tags forward to the newest revision.
-- **Support Menu** introduces the user-facing support surface that exposes Latest Features and Send Feedback outside the admin-only experience.
-- **User-Facing Latest Features in General Settings** gives admins a direct visual reminder that the General tab controls which latest-feature cards are shared with end users.
-- **Fact Memory** explains the new Instructions-versus-Facts model, the profile memory manager, and the dedicated memory-thought and citation visibility users now see in chat.
+### Shared Release Metadata
+- The support latest-features catalog is now grouped by release metadata instead of behaving like one flat list only.
+- The current release remains the primary `Latest Features` section.
+- A new `Previous Release Features` group preserves the earlier `v0.239.001` release highlights.
+- Visibility still uses the same per-feature setting keys, so existing admin sharing choices continue to work.
+
+### User-Facing Latest Features Page
+- The user-facing Support > Latest Features page still renders the current release cards directly.
+- Previous Release Features now appear below the current cards in a collapsed section.
+- The previous-release cards reuse the same feature-card layout, guidance, and action-card treatment as the current release items.
+- External guide links now use the public documentation site at `https://microsoft.github.io/simplechat/` for the previous release walkthroughs that already exist there.
+
+### Admin General Settings
+- `General > User-Facing Latest Features` is now grouped by release.
+- The current release checklist stays expanded.
+- The previous release checklist is collapsed by default so admins can preserve N and N-1 visibility without making the settings area too long.
+
+### Admin Latest Features Tab
+- The admin-only Latest Features tab keeps the current release cards as the primary content.
+- A new collapsed `Previous Release Features` card sits after the current release items.
+- Each previous-release item shows its summary, details, guidance, and whether it is currently shared with end users.
+- The admin sidebar submenu now includes a direct link to the Previous Release Features card.
 
 ## Usage Instructions
-- Open **Admin Settings**.
-- Select **Latest Features**.
-- Expand any card to review the feature summary and the saved screenshots.
-- Click any screenshot thumbnail to open a larger preview modal.
-- Use the Release Notifications Registration card to explain what the Registered or Unregistered badge means and where admins can update that status.
-- Use the mirrored toggles when you want to enable Processing Thoughts or Enhanced Citations directly from the overview page.
-- Use the GPT Selection card to direct admins to the AI Models tab when they need to review endpoint availability, confirm the saved default fallback model, or selectively rebind agents in the admin-only review modal.
-- Use the Citation Improvements card to explain how grounded evidence is preserved across follow-up turns.
-- Use the Document Revisioning card to explain why same-name uploads now create a new current version instead of replacing the old file in place.
-- Use the mirrored Redis cache controls when you want to review or update cache settings from the overview page without leaving Latest Features.
-- Use the deployment guidance card if you run the native Python App Service variant and need the Gunicorn startup command.
-- Use the Send Feedback card to jump directly into the admin mailto workflow for bug reports and feature requests.
-- Use the Support Menu card as a communication aid for end-user help and feedback workflows, including the General-tab checklist that controls user-facing latest-feature sharing.
+- Open **Admin Settings** and select **Latest Features** to review the current release summary cards.
+- Expand **Previous Release Features** when you want to revisit the immediately prior release set.
+- Open **General > User-Facing Latest Features** when you want to control which current and previous release items are shared to end users.
+- Open **Support > Latest Features** as an end user to verify the current release appears first and the previous release group appears below it in a collapsed section.
 
 ## Testing and Validation
-- Confirm the Latest Features tab renders in Admin Settings.
-- Confirm each card expands and collapses correctly.
-- Confirm the admin-only Release Notifications Registration card renders first and does not depend on a screenshot asset.
-- Confirm saved screenshots render as thumbnails and open in the larger preview modal.
-- Confirm the saved screenshots render for GPT Selection, including the agent review summary and modal action images, plus Citation Improvements, Document Revisioning, Support Menu, and the General-tab user-facing latest-features checklist.
-- Confirm the Fact Memory card renders with screenshots for the profile entry point, memory manager, and chat recall experience.
-- Confirm the preview modal closes from both the close button and backdrop click.
-- Confirm mirrored settings remain synchronized with the canonical controls in the existing tabs.
-- Confirm Redis mirror controls stay synchronized with the canonical settings in the Scale tab.
-- Confirm the page restores the active tab after save when Latest Features was the current tab.
-- Confirm the Send Feedback card links into the dedicated Send Feedback tab.
\ No newline at end of file
+- Confirm the support catalog exposes both current and previous release groups.
+- Confirm the user-facing Latest Features page renders the current release directly and the previous release in a collapsed section.
+- Confirm previous-release guide links open the public documentation pages when present.
+- Confirm the admin General checklist groups current and previous release items separately.
+- Confirm the admin Latest Features tab contains the collapsed Previous Release Features card.
+- Confirm the admin sidebar submenu can jump directly to the Previous Release Features card.
\ No newline at end of file
diff --git a/docs/explanation/fixes/v0.241.001/GROUP_WORKSPACE_DELETE_MODAL_FIX.md b/docs/explanation/fixes/v0.241.001/GROUP_WORKSPACE_DELETE_MODAL_FIX.md
new file mode 100644
index 00000000..80dab376
--- /dev/null
+++ b/docs/explanation/fixes/v0.241.001/GROUP_WORKSPACE_DELETE_MODAL_FIX.md
@@ -0,0 +1,46 @@
+# Group Workspace Delete Modal Fix (v0.241.004)
+
+## Overview
+Fixed the group workspace document delete flow so the revision-choice modal is always present and behaves the same way as the personal and public workspace pages.
+
+Version Updated: 0.241.004
+
+Implemented in version: **0.241.004**
+
+## Issue Description
+Deleting a document from Group Workspace could show `Delete confirmation dialog is unavailable. Refresh the page and try again.` instead of opening the revision-choice modal.
+
+## Root Cause Analysis
+The group delete modal markup had been embedded inside the `updateGroupStatusAlert()` JavaScript template instead of being rendered as standalone page markup.
+
+When the active group was in the normal active state, that alert content was hidden, so the modal never existed in the DOM. The delete flow then failed closed as designed because its modal readiness guard could not find the dialog elements.
+
+## Technical Details
+Files modified:
+- `application/single_app/templates/group_workspaces.html`
+- `application/single_app/config.py`
+- `functional_tests/test_group_document_delete_modal_wiring.py`
+- `ui_tests/test_workspace_family_document_revision_delete_modal.py`
+
+Code changes summary:
+- Moved the group delete modal into standalone template markup in the content block.
+- Removed the modal markup from the group status alert `innerHTML` template.
+- Updated the workspace-family UI regression test to verify the modal exists before the delete action is triggered.
+- Added a functional regression test that checks the group template keeps the modal outside the alert injection block.
+
+Testing approach:
+- Functional template-wiring regression coverage.
+- Workspace-family UI regression coverage for personal, group, and public delete flows.
+
+## Validation
+Test results:
+- The group delete flow now has a real page-level modal available on initial load.
+- The fail-closed path still remains in place if the modal is actually removed or missing.
+
+Before/after comparison:
+- Before: group delete could fail immediately because no delete modal existed in the DOM for active groups.
+- After: group delete opens the same revision-choice modal pattern used by the other workspace pages.
+
+User experience improvements:
+- Group document deletion is now consistent with personal and public workspaces.
+- Users can choose between deleting the current revision or all revisions instead of getting blocked by missing modal wiring.
\ No newline at end of file
diff --git a/docs/how-to/upgrade_paths.md b/docs/how-to/upgrade_paths.md
index 50d70c00..9e22ac61 100644
--- a/docs/how-to/upgrade_paths.md
+++ b/docs/how-to/upgrade_paths.md
@@ -134,8 +134,9 @@ This is an **advanced operational option**, not the default repo deployment work
 ### Container Upgrade References
 
 - [AZD deployment guide](../reference/deploy/azd-cli_deploy.md)
-- [Bicep deployment guide](../../deployers/bicep/README.md)
-- [Terraform deployment guide](../../deployers/terraform/ReadMe.md)
+- [Azure CLI with PowerShell deployment guide](../reference/deploy/azurecli_powershell_deploy.md)
+- [Bicep deployment guide](../reference/deploy/bicep_deploy.md)
+- [Terraform deployment guide](../reference/deploy/terraform_deploy.md)
 
 ## Summary
 
diff --git a/docs/latest-release/agent-operations.md b/docs/latest-release/agent-operations.md
new file mode 100644
index 00000000..d0870612
--- /dev/null
+++ b/docs/latest-release/agent-operations.md
@@ -0,0 +1,23 @@
+---
+layout: page
+title: "Agent Operations"
+description: "How agent and action workflows are easier to browse, manage, and validate"
+section: "Latest Release"
+---
+
+Agent Operations updates improve how teams browse, manage, and reason about reusable AI assistants and their connected actions.
+
+## Why It Matters
+
+Advanced agent workflows are only useful when users can find the right assistant quickly and trust the connected tools behind it.
+
+## How to Try It
+
+1. Open **Personal Workspace** if your environment exposes per-user agents and actions.
+2. Switch between list and grid views depending on whether you want denser detail or faster scanning.
+3. Review connected actions carefully when you want to understand what an agent can do.
+
+## Notes
+
+- Availability depends on Personal Workspace, Semantic Kernel, and related agent settings in your environment.
+- Some workflows may also expose inline operational checks such as SQL connection validation.
\ No newline at end of file
diff --git a/docs/latest-release/ai-transparency.md b/docs/latest-release/ai-transparency.md
new file mode 100644
index 00000000..61b91d8d
--- /dev/null
+++ b/docs/latest-release/ai-transparency.md
@@ -0,0 +1,23 @@
+---
+layout: page
+title: "AI Transparency"
+description: "How processing-thought visibility gives users clearer feedback during response generation"
+section: "Latest Release"
+---
+
+AI Transparency adds clearer visibility into the assistant's in-flight work when your team chooses to expose it.
+
+## Why It Matters
+
+Longer responses feel less opaque when users can see progress instead of guessing whether a request stalled.
+
+## How to Try It
+
+1. Open **Chat** and send a prompt that takes long enough to show processing states.
+2. Watch for **Processing Thoughts** while the response is being generated.
+3. Compare the experience with and without the feature enabled in environments where admins control the setting.
+
+## Notes
+
+- This feature is admin-controlled, so some environments may not show it.
+- It is most noticeable on prompts that take more than a moment to complete.
\ No newline at end of file
diff --git a/docs/latest-release/background-chat.md b/docs/latest-release/background-chat.md
new file mode 100644
index 00000000..42ec7d26
--- /dev/null
+++ b/docs/latest-release/background-chat.md
@@ -0,0 +1,23 @@
+---
+layout: page
+title: "Background Chat"
+description: "How long-running chat requests can finish in the background while you keep working"
+section: "Latest Release"
+---
+
+Background Chat lets a long-running request keep working after you move away from the chat page. When the response completes, the app can notify you so you can jump back into the finished conversation.
+
+## Why It Matters
+
+This is most useful for larger uploads and heavier prompts, where waiting on one screen makes the app feel blocked.
+
+## How to Try It
+
+1. Start a longer request from **Chat** the same way you normally would.
+2. If the request takes a while, keep working elsewhere in the app.
+3. Return to the finished result when the completion notification appears.
+
+## Notes
+
+- This experience is designed for long-running requests that would otherwise keep you waiting on the chat page.
+- The notification gives users a cleaner way to return to the completed response.
\ No newline at end of file
diff --git a/docs/latest-release/citation-improvements.md b/docs/latest-release/citation-improvements.md
new file mode 100644
index 00000000..5cb1ddeb
--- /dev/null
+++ b/docs/latest-release/citation-improvements.md
@@ -0,0 +1,23 @@
+---
+layout: page
+title: "Citation Improvements"
+description: "How enhanced citations improve source traceability and follow-up grounding"
+section: "Latest Release"
+---
+
+Citation Improvements help users see where answers came from and keep grounded evidence available across follow-up questions.
+
+## Why It Matters
+
+Better citation carry-forward means fewer follow-up turns lose context or force users to rebuild the same evidence chain from scratch.
+
+## How to Try It
+
+1. Start a grounded conversation in **Chat**.
+2. Open the citations or previews when you want to inspect the source material behind an answer.
+3. Stay in the same conversation for follow-up questions so the assistant can reuse the earlier grounded evidence.
+
+## Notes
+
+- This feature is most noticeable in longer grounded conversations.
+- Users benefit most when they keep related follow-up questions in the same chat thread.
\ No newline at end of file
diff --git a/docs/latest-release/deployment.md b/docs/latest-release/deployment.md
new file mode 100644
index 00000000..423c7515
--- /dev/null
+++ b/docs/latest-release/deployment.md
@@ -0,0 +1,23 @@
+---
+layout: page
+title: "Deployment"
+description: "How deployment guidance and diagnostics improve rollout stability and operational clarity"
+section: "Latest Release"
+---
+
+Deployment updates focus on making configuration, startup validation, and operational guidance easier for admins to follow.
+
+## Why It Matters
+
+For most users this shows up as a more stable rollout of new capabilities rather than a brand-new button in the interface.
+
+## Where to Look
+
+1. Review **Admin Settings** and deployment documentation when rolling out a new environment or troubleshooting startup issues.
+2. Use the improved guidance when validating runtime configuration, especially for hosted deployments.
+3. Recheck deployment notes if a newly announced feature is not visible yet in your environment.
+
+## Notes
+
+- This is mainly an operational improvement managed by admins.
+- End users will usually notice it indirectly through smoother feature rollout and fewer environment issues.
\ No newline at end of file
diff --git a/docs/latest-release/document-versioning.md b/docs/latest-release/document-versioning.md
new file mode 100644
index 00000000..464cbade
--- /dev/null
+++ b/docs/latest-release/document-versioning.md
@@ -0,0 +1,23 @@
+---
+layout: page
+title: "Document Versioning"
+description: "How same-name uploads become revisions so users can work with the right document version"
+section: "Latest Release"
+---
+
+Document Versioning keeps same-name uploads organized as revisions so newer files become current without erasing the older record.
+
+## Why It Matters
+
+Ongoing chats and citations can stay tied to the right version while teams continue updating the same document over time.
+
+## How to Try It
+
+1. Upload an updated file with the same name as an existing document.
+2. Open the workspace document list and confirm which revision is current.
+3. Continue asking questions against the current version when you want the newest content to drive the conversation.
+
+## Notes
+
+- You do not need to delete the older file first unless you no longer want to keep its history.
+- Same-name uploads are treated as revisions rather than destructive replacements.
\ No newline at end of file
diff --git a/docs/latest-release/fact-memory.md b/docs/latest-release/fact-memory.md
new file mode 100644
index 00000000..a3d8ff43
--- /dev/null
+++ b/docs/latest-release/fact-memory.md
@@ -0,0 +1,25 @@
+---
+layout: page
+title: "Fact Memory"
+description: "How Instructions and Facts help the assistant remember durable preferences and relevant personal context"
+section: "Latest Release"
+---
+
+Fact Memory gives each user a compact profile experience for saving **Instructions** and **Facts**. Instructions act like durable response preferences, while Facts are recalled only when they are relevant to the current request.
+
+## Why It Matters
+
+Users no longer need to restate the same preferences or personal context in every conversation, and the chat experience can now show when saved instructions and facts were actually used.
+
+## How to Try It
+
+1. Open your **Profile** page and go to the Fact Memory area.
+2. Save an **Instruction** for a durable preference such as tone, brevity, or formatting.
+3. Save a **Fact** for personal context that should only be recalled when relevant.
+4. Try a chat prompt such as "tell me all about myself" to confirm what the assistant can recall.
+
+## Notes
+
+- Instructions are always applied unless the current prompt overrides them.
+- Facts are recalled only when they are relevant to the current request.
+- The chat experience can surface memory usage through dedicated thought and citation entries.
\ No newline at end of file
diff --git a/docs/latest-release/gpt-selection.md b/docs/latest-release/gpt-selection.md
new file mode 100644
index 00000000..5cc2dcb9
--- /dev/null
+++ b/docs/latest-release/gpt-selection.md
@@ -0,0 +1,23 @@
+---
+layout: page
+title: "GPT Selection"
+description: "How users can choose among available GPT models for different tasks"
+section: "Latest Release"
+---
+
+GPT Selection gives users a clearer way to choose the model that best fits a task when multiple options are available.
+
+## Why It Matters
+
+Different prompts often need different tradeoffs in speed, cost, or reasoning depth, so a visible model picker makes those choices easier.
+
+## How to Try It
+
+1. Open **Chat** and look for the model picker in the composer toolbar.
+2. Try another model when you need faster output, stronger reasoning, or a different cost profile.
+3. Compare results across models for the same prompt when you want to understand the differences in behavior.
+
+## Notes
+
+- Model availability depends on how your admins configured model endpoints and defaults.
+- Some environments may expose only one model, in which case no real selection is needed.
\ No newline at end of file
diff --git a/docs/latest-release/guided-tutorials.md b/docs/latest-release/guided-tutorials.md
new file mode 100644
index 00000000..cee53f05
--- /dev/null
+++ b/docs/latest-release/guided-tutorials.md
@@ -0,0 +1,24 @@
+---
+layout: page
+title: "Guided Tutorials"
+description: "How guided walkthroughs help users learn chat and workspace flows inside the app"
+section: "Latest Release"
+---
+
+Guided Tutorials add in-product walkthroughs so users can learn the interface in context instead of hunting through menus first. Tutorial launchers are shown by default and can be hidden or restored later from the profile page.
+
+## Why It Matters
+
+The fastest way to learn a new workflow is usually inside the workflow itself, with the right controls highlighted as you go.
+
+## How to Try It
+
+1. Start with the **Chat Tutorial** to learn message tools, uploads, prompts, and follow-up workflows.
+2. If Personal Workspace is enabled in your environment, open the **Workspace Tutorial** to learn uploads, filters, tags, prompts, agents, and actions.
+3. If you prefer a cleaner interface after onboarding, open your profile page and hide the tutorial launchers for your own account.
+
+## Notes
+
+- Tutorial buttons are visible by default.
+- Workspace tutorials depend on Personal Workspace being enabled in your environment.
+- Users can restore the tutorial buttons later from the same profile preference.
\ No newline at end of file
diff --git a/docs/latest-release/index.md b/docs/latest-release/index.md
index 5d71150c..2f559695 100644
--- a/docs/latest-release/index.md
+++ b/docs/latest-release/index.md
@@ -1,13 +1,103 @@
 ---
 layout: page
-title: "v0.239.001 Release"
-description: "Overview of new features and improvements in v0.239.001"
+title: "Latest Release Highlights"
+description: "Current feature guides with previous release highlights kept for reference"
 section: "Latest Release"
 ---
 
-This release introduces conversation export capabilities, retention policy management, enhanced workspace controls, and a comprehensive document tagging system.
+This page tracks the current set of guides behind the in-app **Latest Features** experience and keeps the earlier `v0.239.001` content available below as **Previous Release Features**.
 
-## New Features
+## Current Release Features
+
+These guides map to the feature set currently highlighted in the app for end users.
+
+### Guided Tutorials
+
+Step-by-step walkthroughs help users discover core chat, workspace, and onboarding flows faster, and each user can now hide the launchers when they no longer need them.
+
+[Read the full guide]({{ '/latest-release/guided-tutorials/' | relative_url }})
+
+### Background Chat
+
+Long-running chat requests can finish in the background while users continue working elsewhere in the app.
+
+[Read the full guide]({{ '/latest-release/background-chat/' | relative_url }})
+
+### GPT Selection
+
+Teams can expose better model-selection options so users can choose the best experience for a task.
+
+[Read the full guide]({{ '/latest-release/gpt-selection/' | relative_url }})
+
+### Tabular Analysis
+
+Spreadsheet and table workflows continue to improve for exploration, filtering, and grounded follow-up questions.
+
+[Read the full guide]({{ '/latest-release/tabular-analysis/' | relative_url }})
+
+### Citation Improvements
+
+Enhanced citations give users better source traceability, document previews, and history-aware grounding.
+
+[Read the full guide]({{ '/latest-release/citation-improvements/' | relative_url }})
+
+### Document Versioning
+
+Document revision visibility has improved so users can work with the right version of shared content.
+
+[Read the full guide]({{ '/latest-release/document-versioning/' | relative_url }})
+
+### Summaries and Export
+
+Conversation summaries and export workflows continue to expand for reporting and follow-up sharing.
+
+[Read the full guide]({{ '/latest-release/summaries-and-export/' | relative_url }})
+
+### Agent Operations
+
+Agent creation, organization, and operational controls keep getting smoother for advanced scenarios.
+
+[Read the full guide]({{ '/latest-release/agent-operations/' | relative_url }})
+
+### AI Transparency
+
+Thought and reasoning transparency options help users better understand what the assistant is doing.
+
+[Read the full guide]({{ '/latest-release/ai-transparency/' | relative_url }})
+
+### Fact Memory
+
+Profile-based memory now distinguishes always-on Instructions from recall-only Facts so the assistant can carry durable preferences and relevant personal context forward more cleanly.
+
+[Read the full guide]({{ '/latest-release/fact-memory/' | relative_url }})
+
+### Deployment
+
+Deployment guidance and diagnostics keep improving so admins can roll out changes with less guesswork.
+
+[Read the full guide]({{ '/latest-release/deployment/' | relative_url }})
+
+### Redis and Key Vault
+
+Caching and secret-management setup guidance has expanded for more secure and predictable operations.
+
+[Read the full guide]({{ '/latest-release/redis-and-key-vault/' | relative_url }})
+
+### Send Feedback
+
+End users can prepare bug reports and feature requests for their SimpleChat admins directly from the Support menu.
+
+[Read the full guide]({{ '/latest-release/send-feedback/' | relative_url }})
+
+### Support Menu
+
+Admins can surface a dedicated Support menu in navigation with Latest Features and Send Feedback entries for end users.
+
+[Read the full guide]({{ '/latest-release/support-menu/' | relative_url }})
+
+## Previous Release Features
+
+The earlier `v0.239.001` release guides remain available here for reference.
 
 ### Conversation Export
 
@@ -15,7 +105,7 @@ Export one or multiple conversations from the Chat page in JSON or Markdown form
 
 [Read the full guide]({{ '/latest-release/export-conversation/' | relative_url }})
 
-### Retention Policy UI
+### Retention Policy
 
 Configure conversation and document retention periods directly from the workspace and group management pages. Choose from preset retention periods ranging from 7 days to 10 years, use the organization default, or disable automatic deletion entirely.
 
@@ -55,7 +145,7 @@ Checkbox-based multi-document and multi-tag filtering in the chat interface, rep
 
 [Read the full guide]({{ '/latest-release/tags-grid-view-chat-filtering/' | relative_url }})
 
-## Bug Fixes
+## Previous Release Bug Fixes
 
 - **Citation Parsing** -- Fixed edge cases where page range references failed to generate correct clickable links when not all pages had explicit reference IDs.
 - **Public Workspace Activation** -- Fixed 403 error when non-owner users tried to activate a public workspace for chat.
diff --git a/docs/latest-release/redis-and-key-vault.md b/docs/latest-release/redis-and-key-vault.md
new file mode 100644
index 00000000..94aeca59
--- /dev/null
+++ b/docs/latest-release/redis-and-key-vault.md
@@ -0,0 +1,23 @@
+---
+layout: page
+title: "Redis and Key Vault"
+description: "How cache and secret-storage guidance support more secure and predictable operations"
+section: "Latest Release"
+---
+
+Redis and Key Vault improvements make it easier for teams to configure caching and secret storage patterns correctly.
+
+## Why It Matters
+
+The practical outcome is usually reliability and performance, with fewer environment-level issues caused by cache or secret misconfiguration.
+
+## Where to Look
+
+1. Review the relevant **Admin Settings** cache configuration when enabling or adjusting Redis.
+2. Use Key Vault-backed secret storage when your environment standardizes on named secrets instead of raw keys.
+3. Revisit the configuration if repeated-access performance or secret-handling setup needs improvement.
+
+## Notes
+
+- This is primarily an admin and operations feature.
+- Users generally notice the results indirectly through better stability and smoother repeated access patterns.
\ No newline at end of file
diff --git a/docs/latest-release/send-feedback.md b/docs/latest-release/send-feedback.md
new file mode 100644
index 00000000..7c918263
--- /dev/null
+++ b/docs/latest-release/send-feedback.md
@@ -0,0 +1,25 @@
+---
+layout: page
+title: "Send Feedback"
+description: "How end users can prepare structured bug reports and feature requests for their SimpleChat admins"
+section: "Latest Release"
+---
+
+Send Feedback opens a guided, text-only email draft workflow so users can report issues or request improvements without leaving the app.
+
+## Why It Matters
+
+Structured feedback gives admins a better starting point for triage than vague messages without context or reproduction details.
+
+## How to Try It
+
+1. Open **Support > Send Feedback**.
+2. Choose **Bug Report** when something is broken, confusing, or behaving differently than expected.
+3. Choose **Feature Request** when you want a new workflow, capability, or quality-of-life improvement.
+4. Complete the guided fields and prepare the email draft addressed to the support recipient configured by your admins.
+
+## Notes
+
+- This workflow depends on admins configuring the support recipient email.
+- The content is intentionally text-only so the draft is easier to review, send, and audit.
+- This page pairs naturally with the broader [Support Menu]({{ '/latest-release/support-menu/' | relative_url }}) experience.
\ No newline at end of file
diff --git a/docs/latest-release/summaries-and-export.md b/docs/latest-release/summaries-and-export.md
new file mode 100644
index 00000000..2f616552
--- /dev/null
+++ b/docs/latest-release/summaries-and-export.md
@@ -0,0 +1,27 @@
+---
+layout: page
+title: "Summaries and Export"
+description: "How conversation summaries and export actions help users reuse and share chat content"
+section: "Latest Release"
+---
+
+Summaries and Export features make it easier to capture, reuse, and share the important parts of a chat session.
+
+## Why It Matters
+
+Long chats often need a reusable summary, a PDF handoff, or a quick per-message export into email or another workflow.
+
+## How to Try It
+
+1. Open an existing conversation with enough content to summarize.
+2. Generate or refresh the conversation summary when you want a compact recap.
+3. Use the export options when you need to share the whole conversation or reuse a single message outside the app.
+
+## Related Guides
+
+- For the earlier multi-conversation export workflow, see [Export Conversation]({{ '/latest-release/export-conversation/' | relative_url }}).
+
+## Notes
+
+- This feature set covers summaries, PDF export, and per-message reuse actions.
+- It is designed for reporting, handoff, and follow-up sharing rather than only archival export.
\ No newline at end of file
diff --git a/docs/latest-release/support-menu.md b/docs/latest-release/support-menu.md
new file mode 100644
index 00000000..b2ec7b7c
--- /dev/null
+++ b/docs/latest-release/support-menu.md
@@ -0,0 +1,28 @@
+---
+layout: page
+title: "Support Menu"
+description: "How admins can expose Latest Features and Send Feedback in one predictable support surface"
+section: "Latest Release"
+---
+
+Support Menu configuration lets admins rename the menu, choose the internal feedback recipient, and decide which user-facing feature announcements are shared.
+
+## Why It Matters
+
+New capabilities are easier to discover when help, feature announcements, and feedback all live in one predictable place.
+
+## How to Try It
+
+1. Ask an admin to enable the **Support** menu for your environment if it is not already visible.
+2. Open **Support > Latest Features** when you want a curated explanation of what changed and why it matters.
+3. Open **Support > Send Feedback** when you want to report something missing, confusing, or especially useful.
+
+## Related Guides
+
+- [Latest Release Highlights]({{ '/latest-release/' | relative_url }})
+- [Send Feedback]({{ '/latest-release/send-feedback/' | relative_url }})
+
+## Notes
+
+- Admins can share feature announcements one item at a time instead of exposing every feature guide at once.
+- The Support menu now acts as the common entry point for both discovery and feedback workflows.
\ No newline at end of file
diff --git a/docs/latest-release/tabular-analysis.md b/docs/latest-release/tabular-analysis.md
new file mode 100644
index 00000000..cc694648
--- /dev/null
+++ b/docs/latest-release/tabular-analysis.md
@@ -0,0 +1,23 @@
+---
+layout: page
+title: "Tabular Analysis"
+description: "How CSV and spreadsheet workflows support grounded exploration and follow-up analysis"
+section: "Latest Release"
+---
+
+Tabular Analysis improves how SimpleChat works with CSV and spreadsheet files for filtering, comparisons, and grounded follow-up questions.
+
+## Why It Matters
+
+You get the most value after the file is uploaded, because the assistant can reason over stored rows and columns instead of only whatever is pasted into one message.
+
+## How to Try It
+
+1. Upload your CSV or XLSX to **Personal Workspace** if it is enabled, or attach the file directly in **Chat** for a quicker one-off analysis.
+2. Ask a first question about the uploaded data.
+3. Continue with follow-up questions so the assistant can stay grounded in the stored tabular content.
+
+## Notes
+
+- Uploading a newer file with the same name creates a new revision; you do not need to delete the previous version first.
+- This works best when the tabular file is uploaded before the follow-up analysis begins.
\ No newline at end of file
diff --git a/docs/reference/deploy/azd-cli_deploy.md b/docs/reference/deploy/azd-cli_deploy.md
index 75cd8ec9..5445f946 100644
--- a/docs/reference/deploy/azd-cli_deploy.md
+++ b/docs/reference/deploy/azd-cli_deploy.md
@@ -1,3 +1,10 @@
+---
+layout: page
+title: "Azure Developer CLI Deployment"
+description: "Deploy Simple Chat with azd up"
+section: "Reference"
+---
+
 # Azure Developer CLI Deployment
 
 Azure Developer CLI (azd) provides the fastest and most automated way to deploy Simple Chat. This method handles resource provisioning, configuration, and application deployment with minimal manual steps.
@@ -10,6 +17,8 @@ Azure Developer CLI (azd) provides the fastest and most automated way to deploy
 - Deploys the application code
 - Sets up monitoring and logging
 
+This is the primary recommended deployment path for the repo.
+
 ## Prerequisites
 
 ### Required Software
diff --git a/docs/reference/deploy/azurecli_powershell_deploy.md b/docs/reference/deploy/azurecli_powershell_deploy.md
new file mode 100644
index 00000000..921083d4
--- /dev/null
+++ b/docs/reference/deploy/azurecli_powershell_deploy.md
@@ -0,0 +1,46 @@
+---
+layout: page
+title: "Azure CLI with PowerShell Deployment"
+description: "Use the script-driven Azure CLI + PowerShell deployer"
+section: "Reference"
+---
+
+# Azure CLI with PowerShell Deployment
+
+This deployer provisions Simple Chat with Azure CLI and PowerShell orchestration.
+
+Use it when you want a script-driven deployment flow without `azd`, or when you want more direct control over sequencing and recovery steps than the default `azd` workflow provides.
+
+## When to Choose This Path
+
+- You want a script-driven deployment flow without `azd`
+- You want more direct control over sequencing and recovery steps
+- You still want the repo's container-based App Service deployment model
+
+## Runtime Model
+
+- This deployer creates a container-based Azure App Service deployment.
+- Gunicorn is started by the container entrypoint in `application/single_app/Dockerfile`.
+- Do not add a native Python App Service startup command for this path.
+
+## Main Files
+
+- `deployers/azurecli/deploy-simplechat.ps1`
+- `deployers/azurecli/destroy-simplechat.ps1`
+
+## Quick Start
+
+1. Review the variables near the top of `deploy-simplechat.ps1`.
+2. Sign in to the target Azure cloud and subscription.
+3. Run the deployer from PowerShell or `pwsh`.
+
+```powershell
+cd deployers/azurecli
+./deploy-simplechat.ps1
+```
+
+## References
+
+- [Setup Instructions](../../setup_instructions.md)
+- [Upgrade Paths](../../how-to/upgrade_paths.md)
+- [Azure CLI deployer README](https://github.com/microsoft/simplechat/blob/main/deployers/azurecli/README.md)
\ No newline at end of file
diff --git a/docs/reference/deploy/bicep_deploy.md b/docs/reference/deploy/bicep_deploy.md
index e69de29b..d292cd3d 100644
--- a/docs/reference/deploy/bicep_deploy.md
+++ b/docs/reference/deploy/bicep_deploy.md
@@ -0,0 +1,37 @@
+---
+layout: page
+title: "Bicep Deployment"
+description: "How the repo's Bicep templates fit into the supported deployment paths"
+section: "Reference"
+---
+
+# Bicep Deployment
+
+The repo's Bicep templates are the infrastructure foundation behind the primary `azd up` deployment flow.
+
+For most teams, the best-supported Bicep experience is to use the [Azure Developer CLI deployment guide](./azd-cli_deploy.md) and let `azd` orchestrate packaging, provisioning, and deployment.
+
+## When to Choose This Path
+
+- You want to inspect or customize the Bicep templates in `deployers/bicep/`
+- You want to understand the infrastructure used by the `azd` deployment flow
+- You are troubleshooting infrastructure behavior or preparing Bicep module changes
+
+## Recommended Workflow
+
+1. Start with the [Azure Developer CLI deployment guide](./azd-cli_deploy.md).
+2. Review or modify the Bicep files under `deployers/bicep/`.
+3. Use `azd provision --preview` or `azd up` to apply those changes through the supported workflow.
+
+## Runtime Model
+
+- The repo's Bicep-based deployment path is container-based Azure App Service.
+- Gunicorn is started by the container entrypoint in `application/single_app/Dockerfile`.
+- Do not add a native Python App Service startup command unless you intentionally switch away from containers.
+
+## References
+
+- [Setup Instructions](../../setup_instructions.md)
+- [Special Deployment Scenarios](../../setup_instructions_special.md)
+- [Enterprise Networking](../../how-to/enterprise_networking.md)
+- [Bicep deployer README](https://github.com/microsoft/simplechat/blob/main/deployers/bicep/README.md)
diff --git a/docs/reference/deploy/index.md b/docs/reference/deploy/index.md
new file mode 100644
index 00000000..80ef7fd4
--- /dev/null
+++ b/docs/reference/deploy/index.md
@@ -0,0 +1,24 @@
+---
+layout: page
+title: "Deployment Reference"
+description: "Choose the right Simple Chat deployment path"
+section: "Reference"
+---
+
+# Deployment Reference
+
+Simple Chat supports multiple deployment paths. If you want the best-supported path with the most current repo guidance, start with **Azure Developer CLI** and run `azd up`.
+
+## Recommended Order
+
+1. [Azure Developer CLI (`azd up`)](./azd-cli_deploy.md)
+2. [Azure CLI with PowerShell](./azurecli_powershell_deploy.md)
+3. [Bicep](./bicep_deploy.md)
+4. [Terraform](./terraform_deploy.md)
+5. [Manual deployment notes](./manual_deploy.md)
+
+## Related Guides
+
+- [Setup Instructions](../../setup_instructions.md)
+- [Upgrade Paths](../../how-to/upgrade_paths.md)
+- [Special Deployment Scenarios](../../setup_instructions_special.md)
\ No newline at end of file
diff --git a/docs/reference/deploy/manual_deploy.md b/docs/reference/deploy/manual_deploy.md
index d8173d57..1a0e9937 100644
--- a/docs/reference/deploy/manual_deploy.md
+++ b/docs/reference/deploy/manual_deploy.md
@@ -1,3 +1,10 @@
+---
+layout: page
+title: "Manual Deployment Notes"
+description: "Use the native Python Azure App Service deployment path when container deployers are not the right fit"
+section: "Reference"
+---
+
 # Manual Deployment Notes
 
 Use this path when deploying SimpleChat to **native Python Azure App Service** instead of the repo's container-based deployers.
diff --git a/docs/reference/deploy/terraform_deploy.md b/docs/reference/deploy/terraform_deploy.md
index 8b449694..5dcb6d78 100644
--- a/docs/reference/deploy/terraform_deploy.md
+++ b/docs/reference/deploy/terraform_deploy.md
@@ -1,4 +1,21 @@
-# Terraform Deployment Notes
+---
+layout: page
+title: "Terraform Deployment"
+description: "Use the Terraform deployer for state-managed infrastructure"
+section: "Reference"
+---
+
+# Terraform Deployment
+
+Use this path when Terraform is the standard infrastructure workflow in your environment and you want the repo's container-based App Service deployment model.
+
+## When to Choose This Path
+
+- Your team standardizes on Terraform state and workflows
+- You want Terraform-managed infrastructure rather than `azd` orchestration
+- You are comfortable publishing the application image before applying infrastructure
+
+## Runtime Model
 
 The current Terraform deployer in this repo provisions a **container-based Azure Linux Web App**.
 
@@ -8,6 +25,10 @@ The current Terraform deployer in this repo provisions a **container-based Azure
 - Gunicorn startup is already handled by the container entrypoint in `application/single_app/Dockerfile`.
 - You do **not** need to configure App Service Stack Settings Startup command for the current Terraform deployment.
 
+## Important Note
+
+Terraform does not build the application image for you. Publish the image to Azure Container Registry first, then point Terraform at the image tag you want App Service to run.
+
 ## If You Switch Terraform to Native Python Later
 
 If you change the Terraform deployment model away from containers and into native Python App Service, deploy the `application/single_app` folder and use this Startup command:
@@ -15,3 +36,9 @@ If you change the Terraform deployment model away from containers and into nativ
 ```bash
 python -m gunicorn -c gunicorn.conf.py app:app
 ```
+
+## References
+
+- [Setup Instructions](../../setup_instructions.md)
+- [Upgrade Paths](../../how-to/upgrade_paths.md)
+- [Terraform deployer README](https://github.com/microsoft/simplechat/blob/main/deployers/terraform/ReadMe.md)
diff --git a/docs/setup_instructions.md b/docs/setup_instructions.md
index 8047c176..3d463665 100644
--- a/docs/setup_instructions.md
+++ b/docs/setup_instructions.md
@@ -13,72 +13,75 @@ nav_links:
 
 ## Summary
 
-The deployers folder has three different IaC technologies to choose from. You will only choose one of them.
+Simple Chat supports several deployment paths, but they are not equal in automation, coverage, or current repo support.
 
-The options are:
+If you want the best-supported path with the most up-to-date guidance, start with **Azure Developer CLI** and run `azd up`. That workflow uses the repo's Bicep templates under the hood and is the primary deployment path reflected across the current README and deployment docs.
+
+Recommended order:
+- [Azure Developer CLI (`azd up`)](#azure-developer-cli-azd-up)
+- [Azure CLI with PowerShell](#azure-cli-with-powershell)
+- [Bicep](#bicep)
+- [Terraform](#terraform)
 - [Manual Deployment](#manual-deployment)
-- [Azure CLI with Powershell](#azure-cli-with-powershell)
-- [BICEP](#bicep)
-- [Terraform](#hashicorp-terraform)
 - [Upgrade Existing Deployments](#upgrade-existing-deployments)
+- [Special Deployment Scenarios](#special-deployment-scenarios)
 
-**Note:** Terraform is the most robust and requires the least manual post-deployment actions at this time.
+Why multiple deployment technologies?
+We want teams to be able to adopt Simple Chat using the deployment tooling that best fits their environment, while still making the most-supported default path clear.
 
-Why three different deployment technologies?
-We wanted to create as much flexibility with the different preferred IaC technologies as possible for quick adoption.
+## Azure Developer CLI (`azd up`)
 
-In addition, this section covers additional configuration items such as 
-- [Special Deployment Scenarios](#special-deployment-scenarios)
+This is the primary recommended deployment path.
 
-## Manual Deployment
+Use it when you want the most automation, the most repo-level guidance, and the fewest manual decisions. `azd up` packages, provisions, and deploys Simple Chat through one workflow, and it uses the repo's Bicep templates behind the scenes.
 
-This is the step by step process required to deploy the infrastructure and configurations needed to run the Simple Chat solution.  This method is discouraged in favor of any of the IaC deployment solutions, however it does contain information that may be useful in debugging configuration difficulties.
+[Azure Developer CLI deployment guide](./reference/deploy/azd-cli_deploy.md)
 
-[Link to manual deployment steps](./setup_instructions_manual.md)
+## Azure CLI with PowerShell
 
-## Upgrade Existing Deployments
+Use this path when you want a script-driven deployment flow without `azd`.
 
-If you already have Simple Chat deployed and only need to update the application, use the dedicated upgrade guide instead of rerunning the full setup flow.
+Azure CLI performs the Azure resource work, while PowerShell handles orchestration, sequencing, and recovery-oriented scripting. This is the next-best fit when you want more direct control than the `azd` workflow provides.
 
-[Link to upgrade paths](./how-to/upgrade_paths.md)
+[Azure CLI with PowerShell deployment guide](./reference/deploy/azurecli_powershell_deploy.md)
 
-## Azure CLI with Powershell
+## Bicep
 
-All Azure resource provisioning happens with Azure CLI. Powershell is used for the control flow of the script only.
+Bicep is the infrastructure layer behind the primary `azd` deployment flow.
 
-This script has been tested in Azure Government only, but should be compatible with other Azure platforms needing only minimal adjustments.
+Use this path when you want to inspect or customize the Bicep modules directly. For most deployments, start with **Azure Developer CLI** instead of treating Bicep as a separate first-choice workflow.
 
-Always make sure to follow the guidance in the comments/notes.
+[Bicep deployment guide](./reference/deploy/bicep_deploy.md)
 
-[Link to Powershell readme](../deployers/azurecli/README.md)
+## Terraform
 
-## BICEP
+Use Terraform when it is the standard infrastructure workflow in your environment.
 
-All Azure resource provisioning happens using BICEP.
+This path manages a container-based Azure App Service deployment, but it expects your application image to be published before you apply the infrastructure changes.
 
-This script has been tested in Azure Government only, but should be compatible with other Azure platforms needing only minimal adjustments.
+[Terraform deployment guide](./reference/deploy/terraform_deploy.md)
 
-Always make sure to follow the guidance in the comments/notes.
+## Manual Deployment
 
-[Link to BICEP readme](../deployers/bicep/README.md)
+This is the step-by-step process required to deploy the infrastructure and configurations needed to run Simple Chat without the repo's container-based deployers.
 
-## Hashicorp Terraform
+This path is useful for native Python App Service scenarios and for understanding the lower-level configuration details, but it is not the preferred starting point when one of the automated deployment paths fits your environment.
 
-All Azure resource provisioning happens using the latest version of HashiCorp Terraform.
+[Link to manual deployment steps](./setup_instructions_manual.md)
 
-This script has been tested in Azure Government only, but should be compatible with other Azure platforms needing only minimal adjustments.
+## Upgrade Existing Deployments
 
-Always make sure to follow the guidance in the comments/notes.
+If you already have Simple Chat deployed and only need to update the application, use the dedicated upgrade guide instead of rerunning the full setup flow.
 
-[Link to Terraform readme](../deployers/terraform/README.md)
+[Link to upgrade paths](./how-to/upgrade_paths.md)
 
 ## Special Deployment Scenarios
 
-The below sections will cover special scenarios outside of the primary solution deployment.
+The sections below cover scenarios that sit alongside the main deployment paths rather than replacing them.
 
 This includes topics such as:
-- Azure Commericial vs Azure Government deployments
-- Managed Identitity configurations
+- Azure Commercial vs Azure Government deployments
+- Managed Identity configurations
 - Enterprise Networking Requirements
 
 [Link to special deployment configurations](./setup_instructions_special.md)
\ No newline at end of file
diff --git a/docs/setup_instructions_manual.md b/docs/setup_instructions_manual.md
index 788934ab..5bd0cd98 100644
--- a/docs/setup_instructions_manual.md
+++ b/docs/setup_instructions_manual.md
@@ -16,7 +16,7 @@
   - [Using Deployment Slots (Recommended for Production/Staging)](#using-deployment-slots-recommended-for-productionstaging)
   - [Using Direct Deployment to Production (Simpler, for Dev/Test or Low Impact Changes)](#using-direct-deployment-to-production-simpler-for-devtest-or-low-impact-changes)
   - [Automate via CI/CD](#automate-via-cicd)
-- [Return to Main](../README.md)
+- [Return to Setup Instructions](./setup_instructions.md)
 
 
 > <a href="#simple-chat---manual-setup-instructions" style="text-decoration: none;">Return to top</a>
diff --git a/docs/setup_instructions_special.md b/docs/setup_instructions_special.md
index 81b4d4b0..9c3f7ca0 100644
--- a/docs/setup_instructions_special.md
+++ b/docs/setup_instructions_special.md
@@ -4,7 +4,7 @@
 - [How to use Managed Identity](#how-to-use-managed-identity)
 - [Enterprise Networking](#enterprise-networking)
 
-- [Return to Main](../README.md)
+- [Return to Setup Instructions](./setup_instructions.md)
 
 
 ## Azure Government Configuration
@@ -31,7 +31,7 @@ To run the application in Azure Government cloud:
 
 ## How to use Managed Identity
 
-> <a href="#simple-chat---setup-instructions" style="text-decoration: none;">Return to top</a>
+> <a href="#simple-chat---special-setup-instructions" style="text-decoration: none;">Return to top</a>
 
 Using Managed Identity allows the App Service to authenticate to other Azure resources securely without needing to store secrets (like API keys or connection strings) in Application Settings.
 
diff --git a/docs/tutorials/getting_started.md b/docs/tutorials/getting_started.md
index 9f8cd2b7..bd100c08 100644
--- a/docs/tutorials/getting_started.md
+++ b/docs/tutorials/getting_started.md
@@ -43,7 +43,7 @@ Follow the prompts to select your subscription, region, and provide required con
 
 ### Option B: Other Deployment Methods
 
-For more deployment options, see our [deployment reference](../reference/deploy/).
+For more deployment options, see our [deployment reference](../reference/deploy/index.md).
 
 ## Step 2: Initial Configuration
 
diff --git a/functional_tests/test_admin_latest_features_tab.py b/functional_tests/test_admin_latest_features_tab.py
index a7ffb457..f9452b3b 100644
--- a/functional_tests/test_admin_latest_features_tab.py
+++ b/functional_tests/test_admin_latest_features_tab.py
@@ -2,8 +2,8 @@
 # test_admin_latest_features_tab.py
 """
 Functional test for admin Latest Features tab.
-Version: 0.240.085
-Implemented in: 0.240.074; 0.240.085
+Version: 0.241.002
+Implemented in: 0.240.074; 0.240.085; 0.241.002
 
 This test ensures that the Admin Settings page exposes the Latest Features tab,
 renders the expected grouped cards, uses the saved feature screenshots, and
@@ -21,7 +21,7 @@
 ADMIN_TEMPLATE = os.path.join(REPO_ROOT, 'application', 'single_app', 'templates', 'admin_settings.html')
 SIDEBAR_TEMPLATE = os.path.join(REPO_ROOT, 'application', 'single_app', 'templates', '_sidebar_nav.html')
 ADMIN_JS = os.path.join(REPO_ROOT, 'application', 'single_app', 'static', 'js', 'admin', 'admin_settings.js')
-FEATURE_DOC = os.path.join(REPO_ROOT, 'docs', 'explanation', 'features', 'LATEST_FEATURES_ADMIN_TAB.md')
+FEATURE_DOC = os.path.join(REPO_ROOT, 'docs', 'explanation', 'features', 'v0.241.002', 'LATEST_FEATURES_ADMIN_TAB.md')
 FEATURE_IMAGE_DIR = os.path.join(REPO_ROOT, 'application', 'single_app', 'static', 'images', 'features')
 
 
@@ -55,6 +55,8 @@ def test_latest_features_template_structure():
         'id="latest-features-redis-card"',
         'id="latest-features-send-feedback-card"',
         'id="latest-features-support-menu-card"',
+        'id="latest-features-previous-release-card"',
+        'id="latestFeaturesPreviousRelease"',
         'id="latestFeatureImageModal"',
         'class="latest-feature-image-frame"',
         'data-latest-feature-image-src="{{ url_for(\'static\', filename=\'images/features/guided_tutorials_chat.png\') }}"',
@@ -73,6 +75,14 @@ def test_latest_features_template_structure():
         'data-latest-feature-image-src="{{ url_for(\'static\', filename=\'images/features/support_menu_entry.png\') }}"',
         'data-latest-feature-image-src="{{ url_for(\'static\', filename=\'images/features/enable_support_menu_for_end_users.png\') }}"',
         'Admin-only workflow:',
+        "release_group.id == 'previous_release'",
+        '<i class="bi bi-clock-history me-2"></i>{{ release_group.label }}',
+        'Keeping them here gives admins a simple N and N-1 view',
+        'Shared with Users',
+        'Hidden from Users',
+        '{% if feature.images %}',
+        'data-latest-feature-image-src="{{ url_for(\'static\', filename=image.path) }}"',
+        '{{ image.label }}',
         'Review Modal Action',
         'General > User-Facing Latest Features',
         'General Tab Feature Sharing'
@@ -211,7 +221,8 @@ def test_latest_features_sidebar_navigation():
         'data-section="latest-features-thoughts-card"',
         'data-section="latest-features-fact-memory-card"',
         'data-section="latest-features-deployment-card"',
-        'data-section="latest-features-support-menu-card"'
+        'data-section="latest-features-support-menu-card"',
+        'data-section="latest-features-previous-release-card"'
     ]
 
     missing_markers = [marker for marker in required_markers if marker not in sidebar_content]
@@ -270,7 +281,8 @@ def test_latest_features_supporting_assets():
     assert os.path.isdir(FEATURE_IMAGE_DIR), 'Missing placeholder image directory for Latest Features'
 
     doc_content = read_text(FEATURE_DOC)
-    assert 'Version Updated: 0.240.085' in doc_content, 'Feature documentation version header missing or incorrect'
+    assert 'Version Updated: 0.241.002' in doc_content, 'Feature documentation version header missing or incorrect'
+    assert 'Previous Release Features' in doc_content, 'Feature documentation should describe the previous release grouping'
 
     required_images = [
         'agent_default_model_review_action.png',
diff --git a/functional_tests/test_group_document_delete_modal_wiring.py b/functional_tests/test_group_document_delete_modal_wiring.py
new file mode 100644
index 00000000..71152d08
--- /dev/null
+++ b/functional_tests/test_group_document_delete_modal_wiring.py
@@ -0,0 +1,65 @@
+# test_group_document_delete_modal_wiring.py
+"""
+Functional test for group document delete modal wiring.
+Version: 0.241.004
+Implemented in: 0.241.004
+
+This test ensures the group workspace delete-choice modal is rendered as
+standalone page markup and is not injected through the dynamic status alert.
+"""
+
+import re
+import sys
+from pathlib import Path
+
+
+REPO_ROOT = Path(__file__).resolve().parents[1]
+CONFIG_FILE = REPO_ROOT / "application" / "single_app" / "config.py"
+GROUP_TEMPLATE_FILE = REPO_ROOT / "application" / "single_app" / "templates" / "group_workspaces.html"
+
+
+def read_text(path: Path) -> str:
+    return path.read_text(encoding="utf-8")
+
+
+def test_group_document_delete_modal_wiring() -> bool:
+    print("Testing group document delete modal wiring...")
+
+    config_content = read_text(CONFIG_FILE)
+    template_content = read_text(GROUP_TEMPLATE_FILE)
+    scripts_start = template_content.index("{% block scripts %}")
+    content_markup = template_content[:scripts_start]
+
+    assert 'VERSION = "0.241.004"' in config_content, "Config version marker is not current."
+
+    for marker in [
+        'id="groupDocumentDeleteModal"',
+        'id="groupDocumentDeleteModalLabel"',
+        'id="groupDocumentDeleteModalBody"',
+        'id="groupDeleteCurrentBtn"',
+        'id="groupDeleteAllBtn"',
+    ]:
+        assert marker in content_markup, f"Missing standalone modal marker before scripts block: {marker}"
+
+    alert_assignment = re.search(r"alertBox\.innerHTML\s*=\s*`([\s\S]*?)`;", template_content)
+    assert alert_assignment is not None, "Could not locate the group status alert template assignment."
+    assert "groupDocumentDeleteModal" not in alert_assignment.group(1), (
+        "Group delete modal should not be injected through alertBox.innerHTML."
+    )
+
+    required_script_markers = [
+        'const groupDocumentDeleteModalElement = document.getElementById(',
+        'function isGroupDocumentDeleteModalReady()',
+        'function promptGroupDeleteMode(documentCount = 1)',
+        'groupDocumentDeleteModal.show();',
+    ]
+    missing_script_markers = [marker for marker in required_script_markers if marker not in template_content]
+    assert not missing_script_markers, f"Missing group delete modal script markers: {missing_script_markers}"
+
+    print("Group document delete modal wiring test passed!")
+    return True
+
+
+if __name__ == "__main__":
+    success = test_group_document_delete_modal_wiring()
+    sys.exit(0 if success else 1)
\ No newline at end of file
diff --git a/functional_tests/test_latest_features_action_links.py b/functional_tests/test_latest_features_action_links.py
new file mode 100644
index 00000000..a137ae16
--- /dev/null
+++ b/functional_tests/test_latest_features_action_links.py
@@ -0,0 +1,140 @@
+#!/usr/bin/env python3
+# test_latest_features_action_links.py
+"""
+Functional test for latest-features action links.
+Version: 0.241.003
+Implemented in: 0.241.003
+
+This test ensures the latest-features configuration exposes direct in-app
+action links, the admin-controlled documentation toggle, and the launch-intent
+handlers that open the requested Chat, Workspace, and Profile workflows.
+"""
+
+from pathlib import Path
+import sys
+
+
+REPO_ROOT = Path(__file__).resolve().parents[1]
+CONFIG_FILE = REPO_ROOT / "application" / "single_app" / "config.py"
+FUNCTIONS_SETTINGS_FILE = REPO_ROOT / "application" / "single_app" / "functions_settings.py"
+SUPPORT_MENU_CONFIG_FILE = REPO_ROOT / "application" / "single_app" / "support_menu_config.py"
+ADMIN_ROUTE_FILE = REPO_ROOT / "application" / "single_app" / "route_frontend_admin_settings.py"
+ADMIN_TEMPLATE_FILE = REPO_ROOT / "application" / "single_app" / "templates" / "admin_settings.html"
+CHAT_ONLOAD_FILE = REPO_ROOT / "application" / "single_app" / "static" / "js" / "chat" / "chat-onload.js"
+CHAT_DOCUMENTS_FILE = REPO_ROOT / "application" / "single_app" / "static" / "js" / "chat" / "chat-documents.js"
+WORKSPACE_INIT_FILE = REPO_ROOT / "application" / "single_app" / "static" / "js" / "workspace" / "workspace-init.js"
+WORKSPACE_TAGS_FILE = REPO_ROOT / "application" / "single_app" / "static" / "js" / "workspace" / "workspace-tags.js"
+PROFILE_TEMPLATE_FILE = REPO_ROOT / "application" / "single_app" / "templates" / "profile.html"
+
+
+def read_text(path: Path) -> str:
+    return path.read_text(encoding="utf-8")
+
+
+def assert_markers(file_path: Path, markers: list[str]) -> None:
+    content = read_text(file_path)
+    missing = [marker for marker in markers if marker not in content]
+    assert not missing, f"Missing markers in {file_path.name}: {missing}"
+
+
+def test_latest_features_action_links() -> bool:
+    print("Testing latest-features action links and launch intents...")
+
+    assert 'VERSION = "0.241.003"' in read_text(CONFIG_FILE), "Config version marker is not current."
+
+    assert_markers(
+        FUNCTIONS_SETTINGS_FILE,
+        [
+            "'enable_support_latest_feature_documentation_links': False",
+        ],
+    )
+
+    assert_markers(
+        SUPPORT_MENU_CONFIG_FILE,
+        [
+            "_SUPPORT_LATEST_FEATURE_DOCS_SETTING_KEY = 'enable_support_latest_feature_documentation_links'",
+            "'/chats?feature_action=conversation_export'",
+            "'/profile?feature_action=retention_policy#retention-policy-settings'",
+            "'/workspace?feature_action=document_tag_system'",
+            "'/workspace?feature_action=workspace_folder_view'",
+            "'/chats?feature_action=multi_workspace_scope_management'",
+            "'/chats?feature_action=chat_document_and_tag_filtering'",
+            "'requires_settings': [_SUPPORT_LATEST_FEATURE_DOCS_SETTING_KEY]",
+            "def get_support_latest_feature_release_groups_for_settings(settings):",
+        ],
+    )
+
+    assert_markers(
+        ADMIN_ROUTE_FILE,
+        [
+            "if 'enable_support_latest_feature_documentation_links' not in settings:",
+            "enable_support_latest_feature_documentation_links = (",
+            "support_latest_feature_release_groups_preview=get_support_latest_feature_release_groups_for_settings(settings)",
+            "'enable_support_latest_feature_documentation_links': enable_support_latest_feature_documentation_links",
+        ],
+    )
+
+    assert_markers(
+        ADMIN_TEMPLATE_FILE,
+        [
+            'id="enable_support_latest_feature_documentation_links"',
+            'Show Simple Chat Documentation Guide Links',
+            'support_latest_feature_release_groups_preview',
+        ],
+    )
+
+    assert_markers(
+        CHAT_DOCUMENTS_FILE,
+        [
+            'export async function ensureSearchDocumentsVisible()',
+            'export function openScopeDropdown()',
+            'export function openTagsDropdown()',
+        ],
+    )
+
+    assert_markers(
+        CHAT_ONLOAD_FILE,
+        [
+            'function clearFeatureActionParam()',
+            'async function handleLatestFeatureLaunch(featureAction)',
+            "case 'conversation_export':",
+            "case 'multi_workspace_scope_management':",
+            "case 'chat_document_and_tag_filtering':",
+            "const featureAction = getUrlParameter('feature_action') || ''",
+        ],
+    )
+
+    assert_markers(
+        WORKSPACE_TAGS_FILE,
+        [
+            'export function setWorkspaceView(view)',
+        ],
+    )
+
+    assert_markers(
+        WORKSPACE_INIT_FILE,
+        [
+            'function handleWorkspaceFeatureAction()',
+            "featureAction === 'document_tag_system'",
+            "featureAction === 'workspace_folder_view'",
+            "showTagManagementModal();",
+            "setWorkspaceView('grid');",
+        ],
+    )
+
+    assert_markers(
+        PROFILE_TEMPLATE_FILE,
+        [
+            'id="retention-policy-settings"',
+            'function handleProfileFeatureAction()',
+            "featureAction !== 'retention_policy'",
+        ],
+    )
+
+    print("Latest-features action link test passed!")
+    return True
+
+
+if __name__ == "__main__":
+    success = test_latest_features_action_links()
+    sys.exit(0 if success else 1)
\ No newline at end of file
diff --git a/functional_tests/test_latest_release_docs_structure.py b/functional_tests/test_latest_release_docs_structure.py
new file mode 100644
index 00000000..18d1431b
--- /dev/null
+++ b/functional_tests/test_latest_release_docs_structure.py
@@ -0,0 +1,90 @@
+#!/usr/bin/env python3
+"""
+Functional test for latest-release documentation structure.
+Version: 0.241.003
+Implemented in: 0.241.002; 0.241.003
+
+This test ensures the docs/latest-release landing page exposes current and
+previous release sections, and that the current latest-feature guides exist as
+individual markdown pages.
+"""
+
+from pathlib import Path
+import sys
+
+
+REPO_ROOT = Path(__file__).resolve().parents[1]
+CONFIG_FILE = REPO_ROOT / "application" / "single_app" / "config.py"
+LATEST_RELEASE_INDEX = REPO_ROOT / "docs" / "latest-release" / "index.md"
+LATEST_RELEASE_DIR = REPO_ROOT / "docs" / "latest-release"
+
+CURRENT_GUIDES = {
+    "guided-tutorials.md": "Guided Tutorials",
+    "background-chat.md": "Background Chat",
+    "gpt-selection.md": "GPT Selection",
+    "tabular-analysis.md": "Tabular Analysis",
+    "citation-improvements.md": "Citation Improvements",
+    "document-versioning.md": "Document Versioning",
+    "summaries-and-export.md": "Summaries and Export",
+    "agent-operations.md": "Agent Operations",
+    "ai-transparency.md": "AI Transparency",
+    "fact-memory.md": "Fact Memory",
+    "deployment.md": "Deployment",
+    "redis-and-key-vault.md": "Redis and Key Vault",
+    "send-feedback.md": "Send Feedback",
+    "support-menu.md": "Support Menu",
+}
+
+
+def read_text(path: Path) -> str:
+    return path.read_text(encoding="utf-8")
+
+
+def test_latest_release_docs_structure() -> bool:
+    print("Testing latest-release documentation structure...")
+
+    config_content = read_text(CONFIG_FILE)
+    index_content = read_text(LATEST_RELEASE_INDEX)
+
+    assert 'VERSION = "0.241.003"' in config_content, "Config version marker is not current."
+
+    required_index_markers = [
+        'title: "Latest Release Highlights"',
+        '## Current Release Features',
+        '## Previous Release Features',
+        '## Previous Release Bug Fixes',
+        'v0.239.001',
+        "{{ '/latest-release/guided-tutorials/' | relative_url }}",
+        "{{ '/latest-release/background-chat/' | relative_url }}",
+        "{{ '/latest-release/gpt-selection/' | relative_url }}",
+        "{{ '/latest-release/tabular-analysis/' | relative_url }}",
+        "{{ '/latest-release/citation-improvements/' | relative_url }}",
+        "{{ '/latest-release/document-versioning/' | relative_url }}",
+        "{{ '/latest-release/summaries-and-export/' | relative_url }}",
+        "{{ '/latest-release/agent-operations/' | relative_url }}",
+        "{{ '/latest-release/ai-transparency/' | relative_url }}",
+        "{{ '/latest-release/fact-memory/' | relative_url }}",
+        "{{ '/latest-release/deployment/' | relative_url }}",
+        "{{ '/latest-release/redis-and-key-vault/' | relative_url }}",
+        "{{ '/latest-release/send-feedback/' | relative_url }}",
+        "{{ '/latest-release/support-menu/' | relative_url }}",
+        "{{ '/latest-release/export-conversation/' | relative_url }}",
+    ]
+    missing_index_markers = [marker for marker in required_index_markers if marker not in index_content]
+    assert not missing_index_markers, f"Missing latest-release index markers: {missing_index_markers}"
+
+    for file_name, title in CURRENT_GUIDES.items():
+        guide_path = LATEST_RELEASE_DIR / file_name
+        assert guide_path.exists(), f"Missing latest-release guide: {file_name}"
+        guide_content = read_text(guide_path)
+        assert 'layout: page' in guide_content, f"Guide missing layout frontmatter: {file_name}"
+        assert f'title: "{title}"' in guide_content, f"Guide missing title frontmatter: {file_name}"
+        assert 'section: "Latest Release"' in guide_content, f"Guide missing Latest Release section marker: {file_name}"
+
+    print("Latest-release documentation structure test passed!")
+    return True
+
+
+if __name__ == "__main__":
+    success = test_latest_release_docs_structure()
+    sys.exit(0 if success else 1)
\ No newline at end of file
diff --git a/functional_tests/test_support_menu_user_feature.py b/functional_tests/test_support_menu_user_feature.py
index b585b15e..78bb3256 100644
--- a/functional_tests/test_support_menu_user_feature.py
+++ b/functional_tests/test_support_menu_user_feature.py
@@ -2,8 +2,8 @@
 """
 Functional test for support menu sidebar visibility, access behavior, and
 latest-feature image preview support.
-Version: 0.240.085
-Implemented in: 0.240.061; 0.240.085
+Version: 0.241.002
+Implemented in: 0.240.061; 0.240.085; 0.241.002
 
 This test ensures the Support menu renders for signed-in app users when enabled,
 the sidebar and top-nav templates expose the expected links, and the user-facing
@@ -79,6 +79,7 @@ def test_support_menu_settings_defaults_and_persistence():
 
     route_markers = [
         "get_support_latest_feature_catalog",
+        "get_support_latest_feature_release_groups",
         "normalize_support_latest_features_visibility",
         "enable_support_menu = form_data.get('enable_support_menu') == 'on'",
         "support_menu_name = form_data.get('support_menu_name', 'Support').strip()",
@@ -105,6 +106,26 @@ def test_support_menu_settings_defaults_and_persistence():
         "'id': 'redis_key_vault'",
         "'id': 'send_feedback'",
         "'id': 'support_menu'",
+        "'id': 'conversation_export'",
+        "'id': 'retention_policy'",
+        "'id': 'owner_only_group_agent_management'",
+        "'id': 'enforce_workspace_scope_lock'",
+        "'id': 'document_tag_system'",
+        "'id': 'workspace_folder_view'",
+        "'id': 'multi_workspace_scope_management'",
+        "'id': 'chat_document_and_tag_filtering'",
+        "'label': 'Previous Release Features'",
+        "'release_version': '0.239.001'",
+        "'href': 'https://microsoft.github.io/simplechat/latest-release/export-conversation/'",
+        "'path': 'images/features/conversation_export.png'",
+        "'path': 'images/features/conversation_export_type_option.png'",
+        "'path': 'images/features/retention_policy-personal_profile.png'",
+        "'path': 'images/features/retention_policy-manage_group.png'",
+        "'path': 'images/features/workspace_scope_lock.png'",
+        "'path': 'images/features/workspace_tags.png'",
+        "'path': 'images/features/workspace_grid_view.png'",
+        "'path': 'images/features/workspace_scopes_in_chat.png'",
+        "'path': 'images/features/chat_tags_including_doc_classification.png'",
         "'path': 'images/features/facts_memory_view_profile.png'",
         "'path': 'images/features/fact_memory_management.png'",
         "'path': 'images/features/facts_citation_and_thoughts.png'",
@@ -130,7 +151,9 @@ def test_support_menu_settings_defaults_and_persistence():
         "'fragment': 'workspace-tutorial-launch'",
         "'fragment': 'upload-area'",
         "'requires_settings': ['enable_user_workspace']",
+        'def get_support_latest_feature_release_groups():',
         'def get_visible_support_latest_features(settings):',
+        'def get_visible_support_latest_feature_groups(settings):',
         'def _normalize_feature_media(feature):',
     ]
     missing_config = [marker for marker in config_markers if marker not in config_content]
@@ -157,6 +180,9 @@ def test_support_menu_admin_template_and_js():
         '{{ feature.title }}',
         'Enable Support Menu for End Users',
         'Deployment and Redis start unchecked because they are mainly admin-facing rollout and infrastructure topics.',
+        "release_group.id == 'previous_release'",
+        "release_group.collapse_id ~ 'Checklist'",
+        'Show {{ release_group.label }}',
         '<i class="bi bi-life-preserver me-2"></i>Support Menu',
     ]
     missing_template = [marker for marker in template_markers if marker not in template_content]
@@ -218,6 +244,8 @@ def test_support_menu_navigation_and_routes():
     route_markers = [
         "@app.route('/support/latest-features')",
         "def support_latest_features():",
+        'get_visible_support_latest_feature_groups',
+        'support_previous_release_feature_groups',
         "render_template(",
         "'latest_features.html'",
         "@app.route('/support/send-feedback')",
@@ -263,11 +291,15 @@ def test_support_menu_feedback_backend_and_templates():
     latest_features_markers = [
         'A curated view of recent updates your admins have chosen to share with end users.',
         '{% if support_latest_features %}',
+        'support_previous_release_feature_groups',
         'support-feature-card',
         'support-feature-gallery',
         'support-feature-thumbnail-trigger',
         'support-feature-thumbnail-title',
         'support-feature-callout',
+        'support-feature-release-panel',
+        'support-feature-release-toggle',
+        'support-feature-release-version',
         'support-feature-guidance-list',
         'support-feature-action-grid',
         'support-feature-action-card',
@@ -281,7 +313,11 @@ def test_support_menu_feedback_backend_and_templates():
         'Why It Matters',
         'How To Try It',
         'Open The Right Page',
+        '{% if action.href %}',
+        '{% if action.is_external %}',
         "url_for(action.endpoint)",
+        'release_group.collapse_id',
+        'Show {{ release_group.label }}',
         'latestFeatureImageModal',
         'latestFeatureImageModalImage',
         '{{ feature.title }}',
diff --git a/functional_tests/test_user_tutorial_visibility_preference.py b/functional_tests/test_user_tutorial_visibility_preference.py
index 6eb8440b..fe2997fe 100644
--- a/functional_tests/test_user_tutorial_visibility_preference.py
+++ b/functional_tests/test_user_tutorial_visibility_preference.py
@@ -2,8 +2,8 @@
 # test_user_tutorial_visibility_preference.py
 """
 Functional test for user tutorial visibility preference.
-Version: 0.240.068
-Implemented in: 0.240.068
+Version: 0.241.003
+Implemented in: 0.240.068; 0.241.002; 0.241.003
 
 This test ensures that guided tutorial launchers remain visible by default,
 users can manage the preference from the profile page, and the Latest Features
@@ -24,7 +24,7 @@
 CHAT_TEMPLATE_FILE = REPO_ROOT / "application" / "single_app" / "templates" / "chats.html"
 WORKSPACE_TEMPLATE_FILE = REPO_ROOT / "application" / "single_app" / "templates" / "workspace.html"
 LATEST_FEATURES_TEMPLATE_FILE = REPO_ROOT / "application" / "single_app" / "templates" / "latest_features.html"
-FEATURE_DOC_FILE = REPO_ROOT / "docs" / "explanation" / "features" / "USER_TUTORIAL_VISIBILITY_PREFERENCE.md"
+FEATURE_DOC_FILE = REPO_ROOT / "docs" / "explanation" / "features" / "v0.241.001" / "USER_TUTORIAL_VISIBILITY_PREFERENCE.md"
 
 
 def read_text(path: Path) -> str:
@@ -45,7 +45,7 @@ def test_user_tutorial_visibility_preference() -> bool:
     latest_features_content = read_text(LATEST_FEATURES_TEMPLATE_FILE)
 
     required_config_markers = [
-        'VERSION = "0.240.068"',
+        'VERSION = "0.241.003"',
     ]
     missing_config = [marker for marker in required_config_markers if marker not in config_content]
     assert not missing_config, f"Missing config markers: {missing_config}"
diff --git a/ui_tests/test_admin_latest_features_previous_release_images.py b/ui_tests/test_admin_latest_features_previous_release_images.py
new file mode 100644
index 00000000..e294f4a5
--- /dev/null
+++ b/ui_tests/test_admin_latest_features_previous_release_images.py
@@ -0,0 +1,78 @@
+# test_admin_latest_features_previous_release_images.py
+"""
+UI test for admin Latest Features previous-release images.
+Version: 0.241.002
+Implemented in: 0.241.002
+
+This test ensures the admin Latest Features page can expand the Previous
+Release Features section and open one of its thumbnails in the shared image
+preview modal.
+"""
+
+import os
+from pathlib import Path
+
+import pytest
+from playwright.sync_api import expect
+
+
+BASE_URL = os.getenv("SIMPLECHAT_UI_BASE_URL", "").rstrip("/")
+ADMIN_STORAGE_STATE = os.getenv("SIMPLECHAT_UI_ADMIN_STORAGE_STATE", "")
+
+
+def _require_base_url():
+    if not BASE_URL:
+        pytest.skip("Set SIMPLECHAT_UI_BASE_URL to run this UI test.")
+
+
+def _require_storage_state():
+    if not ADMIN_STORAGE_STATE or not Path(ADMIN_STORAGE_STATE).exists():
+        pytest.skip("Set SIMPLECHAT_UI_ADMIN_STORAGE_STATE to a valid authenticated Playwright storage state file.")
+
+
+@pytest.mark.ui
+def test_admin_latest_features_previous_release_images(playwright):
+    """Validate that previous-release thumbnails open the shared admin preview modal."""
+    _require_base_url()
+    _require_storage_state()
+
+    browser = playwright.chromium.launch()
+    context = browser.new_context(
+        storage_state=ADMIN_STORAGE_STATE,
+        viewport={"width": 1440, "height": 900},
+    )
+
+    try:
+        page = context.new_page()
+        response = page.goto(f"{BASE_URL}/admin/settings", wait_until="domcontentloaded")
+        assert response is not None, "Expected a navigation response when loading /admin/settings."
+        if response.status in {401, 403, 404}:
+            pytest.skip("Admin settings page was not available for the configured admin session.")
+
+        assert response.ok, f"Expected /admin/settings to load successfully, got HTTP {response.status}."
+        expect(page.locator("#adminSettingsTabContent")).to_be_visible()
+
+        latest_features_pane = page.locator("#latest-features")
+        if latest_features_pane.count() == 0:
+            pytest.skip("Latest Features tab was not available in this environment.")
+
+        previous_release_toggle = page.locator("a[href='#latestFeaturesPreviousRelease']")
+        if previous_release_toggle.count() == 0:
+            pytest.skip("Previous Release Features section was not available in this environment.")
+
+        previous_release_toggle.first.click()
+        expect(page.locator("#latestFeaturesPreviousRelease")).to_be_visible()
+
+        previous_release_thumbnail = page.locator("#latestFeaturesPreviousRelease .latest-feature-thumbnail-trigger").first
+        if previous_release_thumbnail.count() == 0:
+            pytest.skip("No previous-release thumbnails are available in this environment.")
+
+        previous_release_thumbnail.click()
+
+        modal = page.locator("#latestFeatureImageModal")
+        expect(modal).to_be_visible()
+        expect(page.locator("#latestFeatureImageModalImage")).to_be_visible()
+        expect(page.locator("#latestFeatureImageModalLabel")).not_to_be_empty()
+    finally:
+        context.close()
+        browser.close()
\ No newline at end of file
diff --git a/ui_tests/test_latest_features_action_launchers.py b/ui_tests/test_latest_features_action_launchers.py
new file mode 100644
index 00000000..e00e848d
--- /dev/null
+++ b/ui_tests/test_latest_features_action_launchers.py
@@ -0,0 +1,103 @@
+#!/usr/bin/env python3
+# test_latest_features_action_launchers.py
+"""
+UI test for latest-features action launchers.
+Version: 0.241.003
+Implemented in: 0.241.003
+
+This test ensures the latest-feature deep links can open the intended
+workspace, profile, and chat workflows directly from their destination pages.
+"""
+
+import os
+from pathlib import Path
+
+import pytest
+from playwright.sync_api import expect
+
+
+BASE_URL = os.getenv("SIMPLECHAT_UI_BASE_URL", "").rstrip("/")
+STORAGE_STATE = os.getenv("SIMPLECHAT_UI_STORAGE_STATE", "")
+ADMIN_STORAGE_STATE = os.getenv("SIMPLECHAT_UI_ADMIN_STORAGE_STATE", "")
+
+
+def _require_base_url():
+    if not BASE_URL:
+        pytest.skip("Set SIMPLECHAT_UI_BASE_URL to run this UI test.")
+
+
+def _get_storage_state_path() -> str:
+    for candidate in (STORAGE_STATE, ADMIN_STORAGE_STATE):
+        if candidate and Path(candidate).exists():
+            return candidate
+    pytest.skip("Set SIMPLECHAT_UI_STORAGE_STATE or SIMPLECHAT_UI_ADMIN_STORAGE_STATE to a valid authenticated Playwright storage state file.")
+
+
+@pytest.mark.ui
+def test_latest_features_action_launchers(playwright):
+    """Validate that launch-intent links open the requested workspace, profile, and chat workflows."""
+    _require_base_url()
+    storage_state = _get_storage_state_path()
+
+    browser = playwright.chromium.launch()
+    context = browser.new_context(
+        storage_state=storage_state,
+        viewport={"width": 1440, "height": 960},
+    )
+
+    try:
+        page = context.new_page()
+
+        workspace_response = page.goto(f"{BASE_URL}/workspace?feature_action=workspace_folder_view", wait_until="domcontentloaded")
+        assert workspace_response is not None, "Expected a navigation response when loading /workspace."
+        if workspace_response.status in {401, 403, 404}:
+            pytest.skip("Personal Workspace page was not available for the configured session.")
+
+        grid_radio = page.locator("#docs-view-grid")
+        if grid_radio.count() == 0:
+            pytest.skip("Workspace grid-view controls were not available in this environment.")
+
+        expect(grid_radio).to_be_checked()
+        expect(page.locator("#documents-grid-view")).to_be_visible()
+        assert "feature_action=" not in page.url, "Workspace feature_action parameter should be consumed after launch."
+
+        workspace_tags_response = page.goto(f"{BASE_URL}/workspace?feature_action=document_tag_system", wait_until="domcontentloaded")
+        assert workspace_tags_response is not None, "Expected a navigation response when reloading /workspace."
+        if workspace_tags_response.status in {401, 403, 404}:
+            pytest.skip("Personal Workspace tag-management flow was not available for the configured session.")
+
+        tag_management_modal = page.locator("#tagManagementModal")
+        if tag_management_modal.count() == 0:
+            pytest.skip("Workspace tag-management modal was not available in this environment.")
+
+        expect(tag_management_modal).to_be_visible()
+        assert "feature_action=" not in page.url, "Workspace tag-management feature_action parameter should be consumed after launch."
+
+        profile_response = page.goto(f"{BASE_URL}/profile?feature_action=retention_policy#retention-policy-settings", wait_until="domcontentloaded")
+        assert profile_response is not None, "Expected a navigation response when loading /profile."
+        if profile_response.status in {401, 403, 404}:
+            pytest.skip("Profile page was not available for the configured session.")
+
+        retention_section = page.locator("#retention-policy-settings")
+        if retention_section.count() == 0:
+            pytest.skip("Retention policy settings were not enabled in this environment.")
+
+        expect(retention_section).to_be_visible()
+        expect(page.locator("#conversation_retention_days")).to_be_focused()
+        assert "feature_action=" not in page.url, "Profile feature_action parameter should be consumed after launch."
+
+        chat_response = page.goto(f"{BASE_URL}/chats?feature_action=multi_workspace_scope_management", wait_until="domcontentloaded")
+        assert chat_response is not None, "Expected a navigation response when loading /chats."
+        if chat_response.status in {401, 403, 404}:
+            pytest.skip("Chat page was not available for the configured session.")
+
+        search_documents_container = page.locator("#search-documents-container")
+        if search_documents_container.count() == 0:
+            pytest.skip("Chat grounded-search controls were not available in this environment.")
+
+        expect(search_documents_container).to_be_visible()
+        expect(page.locator("#scope-dropdown-button")).to_have_attribute("aria-expanded", "true")
+        assert "feature_action=" not in page.url, "Chat feature_action parameter should be consumed after launch."
+    finally:
+        context.close()
+        browser.close()
\ No newline at end of file
diff --git a/ui_tests/test_support_latest_features_image_modal.py b/ui_tests/test_support_latest_features_image_modal.py
index 77e1a375..b41bf0e6 100644
--- a/ui_tests/test_support_latest_features_image_modal.py
+++ b/ui_tests/test_support_latest_features_image_modal.py
@@ -1,8 +1,8 @@
 # test_support_latest_features_image_modal.py
 """
 UI test for support latest-features image previews.
-Version: 0.240.061
-Implemented in: 0.240.061
+Version: 0.241.002
+Implemented in: 0.240.061; 0.241.002
 
 This test ensures the user-facing Latest Features page opens a full-size image
 preview modal when a feature thumbnail is clicked and keeps the expanded
@@ -58,6 +58,21 @@ def test_support_latest_features_image_modal(playwright):
         expect(page.locator(".support-feature-callout").first).to_be_visible()
         expect(page.locator(".support-feature-action-card").first).to_be_visible()
 
+        previous_release_toggle = page.get_by_role("button", name="Show Previous Release Features")
+        if previous_release_toggle.count() > 0:
+            previous_release_toggle.first.click()
+            expect(page.locator("#supportLatestFeaturesPreviousRelease")).to_be_visible()
+            expect(page.get_by_role("heading", name="Previous Release Features")).to_be_visible()
+
+            previous_release_thumbnail = page.locator("#supportLatestFeaturesPreviousRelease .support-feature-thumbnail-trigger").first
+            if previous_release_thumbnail.count() > 0:
+                previous_release_thumbnail.click()
+                modal = page.locator("#latestFeatureImageModal")
+                expect(modal).to_be_visible()
+                expect(page.locator("#latestFeatureImageModalImage")).to_be_visible()
+                page.locator("#latestFeatureImageModal .btn-close").click()
+                expect(modal).not_to_be_visible()
+
         thumbnail_trigger = page.locator(".support-feature-thumbnail-trigger").first
         if thumbnail_trigger.count() == 0:
             pytest.skip("No latest-feature images are available in this environment.")
diff --git a/ui_tests/test_workspace_family_document_revision_delete_modal.py b/ui_tests/test_workspace_family_document_revision_delete_modal.py
index 73c6644c..c96391e7 100644
--- a/ui_tests/test_workspace_family_document_revision_delete_modal.py
+++ b/ui_tests/test_workspace_family_document_revision_delete_modal.py
@@ -1,8 +1,8 @@
 # test_workspace_family_document_revision_delete_modal.py
 """
 UI test for workspace-family document revision delete modals.
-Version: 0.240.056
-Implemented in: 0.240.056
+Version: 0.241.004
+Implemented in: 0.241.004
 
 This test ensures the personal, group, and public workspace pages use a
 Bootstrap revision delete modal instead of a native browser confirm dialog,
@@ -47,9 +47,12 @@ def on_dialog(dialog):
     assert response.ok, f"Expected {page_path} to load successfully, got HTTP {response.status}."
     expect(page.locator(ready_selector)).to_be_visible()
 
+    modal = page.locator(modal_selector)
+    expect(modal).to_have_count(1)
+    expect(modal).to_be_hidden()
+
     page.evaluate(trigger_script)
 
-    modal = page.locator(modal_selector)
     expect(modal).to_be_visible()
     expect(modal.get_by_role("button", name="Delete Current Version")).to_be_visible()
     expect(modal.get_by_role("button", name="Delete All Versions")).to_be_visible()