What Are Perplexity Spaces? Meaning, Sources, and Sharing

Perplexity Spaces are the research workspaces now continued as Projects in Perplexity. They bring related work together around a topic or goal, while an individual research thread holds one conversation and its follow-up questions.

The name matters when you look for the feature: Perplexity says existing Spaces migrate automatically to Projects in its workspace announcement↗ (opens in a new tab). Older guides still use Spaces and threads, while current documentation uses Projects and sessions. This article explains the underlying idea so those labels make sense.

When research becomes ongoing work, fenbs keeps the project tasks, human decisions, and next steps available to connected AI assistants beyond the research conversation.

What does the workspace bring together?

Think of it as a named home for a continuing subject. A single search might answer which document contains a requirement. The larger workspace gives that investigation a place alongside other questions about the same project. The benefit is organization: you can recognize which work belongs together before opening every conversation.

Perplexity’s Projects guide↗ (opens in a new tab) describes a hub for searches, Computer tasks, files, instructions, and connected tools. Its scope therefore goes beyond a folder of search answers. You do not need every capability to understand its basic purpose: related work has a common home.

How is it different from a research thread?

A thread is the conversation itself. Perplexity’s session documentation↗ (opens in a new tab) describes the initial question, follow-ups, responses, and sources as parts of one session. Asking “Which of those options meets our requirement?” continues that discussion rather than starting the whole explanation again.

The workspace is the broader subject. Say a designer is researching an arts organization’s website. One conversation explores calendar accessibility; another examines donation forms; a third investigates image permissions. Those are different investigations with a shared purpose. Grouping them helps a colleague find the right starting point without treating one very long conversation as the entire project.

Finding the discussion still leaves the question of what to do next. In fenbs, a task can carry that follow-up through a kanban board, with its status separate from the research that informed it.

What do sources and instructions each do?

Sources are material to consult; instructions describe how to work with it. Current Projects support persistent files, prioritized web links or domains, and instructions used for queries in the project. Files added from connected sources are copies: changes to the original do not automatically update that project copy. Check those details in the Projects guide linked above before relying on a document being current.

For the arts website, a source might be an approved accessibility checklist. An instruction might say, “Identify the checklist item behind each recommendation, and flag anything the document does not answer.” The instruction cannot make an outdated checklist current or turn an unsupported suggestion into evidence.

• Name the research boundary: which project, audience, location, and documents matter.
• Describe the answer you need: a short explanation, comparison, or list of unresolved questions.
• Keep uncertainty visible: ask for missing evidence instead of a confident guess.
• Check important claims against the original material before using them in a decision.

A useful test is whether another person could explain why a source belongs here. If the answer is only “it might be useful someday,” leave it out until it answers a real question. A focused collection is easier to review than a miscellaneous archive.

What does sharing actually share?

Sharing gives other people access to the workspace; it is separate from distributing one answer. Current Projects are private by default and cannot be publicly shared. Perplexity’s Enterprise permissions guide↗ (opens in a new tab) distinguishes project invitations and eligible organization sharing from public links for individual sessions or Pages. Older Spaces instructions about public sharing can therefore mislead.

Before inviting someone, review the material you intend them to use. A project for an outside collaborator should contain the research they need, with unrelated internal material kept elsewhere. Explain which findings are approved, which remain questions, and who can settle those questions. Access to research is useful; a clear understanding of its status makes that access usable.

Use a specific project name as well. “Spring exhibition website” tells a collaborator more than “Research.” A short description of the goal and the decision it supports helps prevent someone from applying last project’s answer to this project’s problem.

Is this the same as an AI memory?

Organization and memory are related ideas, but the labels describe different things. A workspace collects work under a common subject. Perplexity also documents Brain↗ (opens in a new tab), a memory system for Computer that learns from activity and corrections. Its availability and controls belong to Perplexity’s current documentation rather than older Spaces tutorials.

For your own work, ask a concrete question: can the next session tell a verified finding from an open question? Keeping material together helps, but you should still record that distinction explicitly. A helpful answer is not the same thing as a decision someone has approved.

What should continue after the research?

Save the parts that change the next action: the question investigated, the source supporting the answer, the person who chose a direction, and the work still required. Keep those records short enough that a colleague can check them. Link to the longer investigation rather than repeating every exchange.

In the example, research might suggest two accessible calendars. The team still needs to choose one, test it, and record the result. fenbs can keep those tasks and decisions, while the Perplexity MCP guide addresses Perplexity connection questions separately. Do not assume that a connection in one AI app transfers another app’s research history.

How to do this with fenbs

1. Create a free account. fenbs is free for one person, no credit card. Add a project with the same clear goal as your research workspace.
2. Add a short AI context note with reviewed findings, source links, and unanswered questions. Copy only the material you have checked and are allowed to share.
3. Record the choices a person made in Decisions and rules. Add tasks for implementation or further checks; leave unanswered decisions open.
4. Connect a supported AI app through the integration instructions. Ask it to read the project context before working and save task progress and Where we left off before stopping.

fenbs does not import your Perplexity conversations. If your whole job is asking questions and reading the answers inside Perplexity, another work record may add unnecessary upkeep. It becomes useful when approved findings need to guide tasks, teammates, or sessions in other AI apps.

For the next question, use the setup guide, NotebookLM comparison, or alternatives guide. If you are looking for missing work, see Spaces disappeared; for fit and limitations, read the Spaces review. More workplace guidance is in AI at work.