Spaces: Building Team Knowledge Bases In Perplexity

Spaces are Perplexity's project containers — system prompts, files, and shared chat history. They turn the search engine into a research workspace.

10 min · Reviewed 2026

What a Space is

A Space is a folder with a system prompt, a set of attached files, optional URL allow-lists, and a shared thread history. Inside a Space, Perplexity follows the instructions you set and weights your uploaded files higher than the open web. Outside a Space, it forgets all of that.

What Spaces are good for

Ongoing research projects with returning context (a market scan, a thesis, a customer)
Team knowledge bases where multiple people query the same docs
Persistent personas — 'always answer as a skeptical M&A analyst'
Document Q&A with the open web as a fallback when the docs are silent
Course-style learning where you upload syllabus + readings

Where Spaces fall short

Spaces are not a full document management system. There is no permission hierarchy inside a Space — anyone with access sees everything. Files are not chunked or indexed the way a purpose-built RAG system would do them. For a 1000-document corpus, a custom pipeline still wins. For 5-50 docs, Spaces is the fastest setup on the market.

Need	Spaces	Custom RAG	ChatGPT Project
5-50 docs, fast setup	Best	Overkill	Strong
Cited answers by default	Best	Build it	Toggle on
Hundreds of docs, search quality	Stretches	Best	Stretches
Team-shared workspace	Yes	Build it	Workspace plan
Web fallback when docs silent	Yes	Build it	Yes

Build a Space in five minutes

Pick one current project. Don't make a generic 'work' Space
Write a 4-line system prompt: role, audience, citation rule, fallback rule
Upload the 10 most relevant docs
Run three test queries you'd realistically ask
Iterate the system prompt until the answers feel right

The big idea: a Space is a Perplexity that knows your project. Build them per-project, not as one mega-space, and treat the system prompt as the contract.

End-of-lesson check

8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-perplexity-spaces-creators

What is the main idea of "Spaces: Building Team Knowledge Bases In Perplexity"?
1. Spaces are Perplexity's project containers — system prompts, files, and shared chat history. They turn the search engine into a research workspace.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "Spaces: Building Team Knowledge Bases In Perplexity"?
1. system prompt
2. spaces
3. file uploads
4. shared workspace
Which use of AI fits this topic best?
1. Let the AI decide what matters without your review
2. Use the answer before checking whether it fits the situation
3. Ongoing research projects with returning context (a market scan, a thesis, a customer)
4. Treat the AI output as automatically correct
What should a careful learner remember about "Anatomy of a great Space"?
1. Use "Anatomy of a great Space" as a reminder to verify the AI output before anyone relies on it.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use AI for drafting and comparison, but verify before publishing or relying on it.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about spaces be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about spaces.
Which action would help you apply "Spaces: Building Team Knowledge Bases In Perplexity" responsibly?
1. Use the tool to avoid thinking through the tradeoff
2. Keep going even if the output conflicts with a trusted source
3. Treat the AI output as automatically correct
4. Team knowledge bases where multiple people query the same docs

← Back to interactive lesson

Tendril · Creators · Tools Literacy