Issue
When a user can access a public workspace but has hidden it from the public workspace directory/chat scope, opening that workspace directly and choosing Chat on a document carries the document selection into the chat UI, but the document is not actually searched.
Steps to Reproduce
- Mark an accessible public workspace as hidden in the public workspace directory.
- Open that public workspace directly.
- Choose Chat for a processed document, or select documents and choose the bulk chat action.
- Ask a question that should be answered from the selected document.
Expected Behavior
The chosen workspace is added to the current user's visible public workspaces without hiding any other visible workspaces. It appears in the chat workspace selector, and the selected document is included in grounded search.
Actual Behavior
The chat page can appear to carry the document selection, but the hidden workspace is absent from the chat selector and the visible-workspace documents endpoint excludes its documents, so the answer is not grounded in the selected file.
Impact
Users receive misleading UI state and answers that silently omit the document they explicitly chose.
Notes
The public workspace document and bulk-chat handoffs navigate with workspace_id, while chat document loading is intentionally filtered by the user's publicDirectorySettings. The repository already has additive public-workspace visibility helpers, so the fix should preserve existing visible workspaces.
Issue
When a user can access a public workspace but has hidden it from the public workspace directory/chat scope, opening that workspace directly and choosing Chat on a document carries the document selection into the chat UI, but the document is not actually searched.
Steps to Reproduce
Expected Behavior
The chosen workspace is added to the current user's visible public workspaces without hiding any other visible workspaces. It appears in the chat workspace selector, and the selected document is included in grounded search.
Actual Behavior
The chat page can appear to carry the document selection, but the hidden workspace is absent from the chat selector and the visible-workspace documents endpoint excludes its documents, so the answer is not grounded in the selected file.
Impact
Users receive misleading UI state and answers that silently omit the document they explicitly chose.
Notes
The public workspace document and bulk-chat handoffs navigate with
workspace_id, while chat document loading is intentionally filtered by the user'spublicDirectorySettings. The repository already has additive public-workspace visibility helpers, so the fix should preserve existing visible workspaces.