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

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

What is the core idea behind "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. lesson design
3. Run on Reddit, save the answer
4. Perplexity can collect sources; Tendril lessons need judgment.
Which term best describes a foundational idea in "Spaces: Building Team Knowledge Bases In Perplexity"?
1. system prompt
2. space
3. scoped retrieval
4. shared workspace
A learner studying Spaces: Building Team Knowledge Bases In Perplexity would need to understand which concept?
1. space
2. scoped retrieval
3. system prompt
4. shared workspace
Which of these is directly relevant to Spaces: Building Team Knowledge Bases In Perplexity?
1. space
2. system prompt
3. shared workspace
4. scoped retrieval
Which of the following is a key point about Spaces: Building Team Knowledge Bases In Perplexity?
1. Ongoing research projects with returning context (a market scan, a thesis, a customer)
2. Team knowledge bases where multiple people query the same docs
3. Persistent personas — 'always answer as a skeptical M&A analyst'
4. Document Q&A with the open web as a fallback when the docs are silent
Which of these does NOT belong in a discussion of Spaces: Building Team Knowledge Bases In Perplexity?
1. Ongoing research projects with returning context (a market scan, a thesis, a customer)
2. Persistent personas — 'always answer as a skeptical M&A analyst'
3. Team knowledge bases where multiple people query the same docs
4. lesson design
Which statement is accurate regarding Spaces: Building Team Knowledge Bases In Perplexity?
1. Write a 4-line system prompt: role, audience, citation rule, fallback rule
2. Upload the 10 most relevant docs
3. Pick one current project. Don't make a generic 'work' Space
4. Run three test queries you'd realistically ask
Which of these does NOT belong in a discussion of Spaces: Building Team Knowledge Bases In Perplexity?
1. Upload the 10 most relevant docs
2. Pick one current project. Don't make a generic 'work' Space
3. Write a 4-line system prompt: role, audience, citation rule, fallback rule
4. lesson design
What is the key insight about "Anatomy of a great Space" in the context of Spaces: Building Team Knowledge Bases In Perplexity?
1. Title that names the project. System prompt that defines tone, audience, and what to do when sources disagree.
2. lesson design
3. Run on Reddit, save the answer
4. Perplexity can collect sources; Tendril lessons need judgment.
What is the key insight about "Don't dump confidential data without a plan" in the context of Spaces: Building Team Knowledge Bases In Perplexity?
1. lesson design
2. Spaces sit on Perplexity's infrastructure with their data terms.
3. Run on Reddit, save the answer
4. Perplexity can collect sources; Tendril lessons need judgment.
What is the key insight about "From the community" in the context of Spaces: Building Team Knowledge Bases In Perplexity?
1. lesson design
2. Run on Reddit, save the answer
3. Heavy Spaces users on Reddit consistently report the same pattern: one Space per project beats one mega-Space, and a tig…
4. Perplexity can collect sources; Tendril lessons need judgment.
Which statement accurately describes an aspect of Spaces: Building Team Knowledge Bases In Perplexity?
1. lesson design
2. Run on Reddit, save the answer
3. Perplexity can collect sources; Tendril lessons need judgment.
4. A Space is a folder with a system prompt, a set of attached files, optional URL allow-lists, and a shared thread history.
What does working with Spaces: Building Team Knowledge Bases In Perplexity typically involve?
1. Spaces are not a full document management system. There is no permission hierarchy inside a Space — anyone with access sees everything.
2. lesson design
3. Run on Reddit, save the answer
4. Perplexity can collect sources; Tendril lessons need judgment.
Which of the following is true about Spaces: Building Team Knowledge Bases In Perplexity?
1. lesson design
2. 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…
3. Run on Reddit, save the answer
4. Perplexity can collect sources; Tendril lessons need judgment.
Which best describes the scope of "Spaces: Building Team Knowledge Bases In Perplexity"?
1. It is unrelated to tools workflows
2. It applies only to the opposite beginner tier
3. It focuses on Spaces are Perplexity's project containers — system prompts, files, and shared chat history. They tu
4. It was deprecated in 2024 and no longer relevant

← Back to interactive lesson

Tendril · Creators · Tools Literacy