Request for Advanced Thread Visibility Control in Spaces: Restrict Threads/Prompts to Assigned Spaces Only

Overview:
I am a frequent user of Perplexity Spaces for organizing projects, collaborating with different teams, and separating personal research from shared work. While Spaces offer powerful collaborative options, I have encountered a significant limitation: threads or prompts linked to a Space still appear in my global Home > Library, rather than being isolated to their respective Space.

Current Behavior & Issue:
Whenever I create or contribute a thread/prompt inside a Space, whether for a personal project or a team collaboration, it automatically shows up in my overall Library view. This means:

  • Every thread, regardless of its relevance or confidentiality, is mixed with my personal history.
  • It becomes difficult to manage context, as Space-specific content and general content are intermixed, cluttering my interface.
  • Threads meant to stay private to a certain group (or context) cannot be kept invisible to the rest of my activity or Library.
  • Over time, this escalates into major organizational challenges, especially as the number of Spaces and collaborative threads grows.

User Scenarios Affected:
-
Teams working on sensitive projects want only members to see relevant prompts, not all account holders’ Library feeds.

  • Researchers and educators using Perplexity to separate coursework, research, or group discussion from their main transcript/history.
  • Users wanting to keep personal brainstorms, drafts, or sensitive work away from their aggregated prompt history for privacy or focus.

Competitive Benchmarks:
-
Other collaboration platforms (Slack channels, Notion workspaces, Google Drive folders) allow content to reside only within a dedicated structure, keeping global views uncluttered and respecting boundaries.

  • These platforms typically provide toggles for visibility, permissions, or “keep private/only in channel/workspace/folder” options.

Feature Proposal:
I propose Perplexity add advanced thread/prompt visibility controls such as:

  • An option or toggle to limit a thread/prompts’ appearance strictly to the Space where it was created, preventing it from surfacing in the Home > Library or global search.
  • This could be configured at thread creation, during a move to a Space, or as a batch action for existing threads.
  • Admins and individual users should be able to select visibility scope, with reminders about privacy and collaboration.

Benefits & Impact:
-
Dramatic reduction in clutter within the Home > Library.

  • Streamlined workflow for users and teams managing multiple Spaces.
  • Enhanced privacy for projects that must remain confidential or just organized.
  • Increased productivity from improved context management—less noise, quicker retrieval.
  • Makes Perplexity more attractive for professional and educational users requiring strict organizational boundaries.

Current Workarounds:
-
Manual deletion of threads from Library, but this also deletes from Spaces, which is an impractical solution.

  • No batch privacy actions, leading to tedious thread management.

Request for Feedback:
I would welcome suggestions, feedback, or input from the Perplexity team and community, especially if there are plans or workarounds I may have missed. Happy to clarify use cases or expand examples if it helps move this forward!

Thank you for considering this enhancement.