Build a Shared Research Hub With Perplexity Projects
By Ashley Gross
·
·
Perplexity

Your team's research doesn't have a knowledge problem. It has a location problem. The pricing deck lives in one inbox, the win/loss notes live in another, and everyone asks the same question twice. A Perplexity Project puts the files, the instructions, and the answers in one place your whole team can query.
What You'll Need
Plan level: Perplexity Pro or Enterprise Pro
Team access: The names or emails of the teammates you want to add
Files: Core documentation (PDFs, DOCX, CSVs, TXT)
Time required: 15 minutes
Step-by-Step Walkthrough
Step 1: Create Your Project
Open the left sidebar and hover over Projects. Click the + button. In the "Create a new project" dialog, add a clear title based on the workflow or department, such as "Competitive Intelligence" or "Product Onboarding." The description is optional. Leave the Brain toggle off for now, since automatic Brain updates use credits. Click Create.
Why it matters: A specific name prevents duplicate Projects and tells your team exactly what context lives inside.


Step 2: Write Project Instructions
Open the Settings tab inside your Project. Under Context, find the Instructions field. Paste your instructions and click Save. This prompt guides every session inside the Project.
Why it matters: Instructions keep every answer on team standards, with consistent citations and your internal documents first.
Weak example: "Answer questions accurately using these files."
Strong example (copyable):
"You are an internal research strategist for The Alliance. Answer all questions using the uploaded documents first. Cite specific document names and page or section numbers whenever possible. If the uploaded files do not contain enough context to answer completely, search the web to supplement the response, but explicitly state which points come from internal files versus external web sources. Tone should be direct, concise, and professional."

Step 3: Upload and Organize Source Files
Open the Files tab and click + New to upload PDFs, Word documents, CSVs, or text files. Click any file name to preview it inside the Project.
Why it matters: These files become the Project's working context, so the quality of your answers depends on what you put here.
Limits to know: On our Pro account, Settings shows a cap of 5,000 saved files and 2.5 GB of storage per Project. Check your own Settings tab, since limits vary by plan.
Keep files focused: Upload clean, well-structured documents with clear section headers. Split giant manuals into logical sections.

Step 4: Set Your Search Defaults
Stay in Settings > Context and scroll down. Two settings shape how the Project searches:
Links: Click Add to list the websites Perplexity should prioritize when it searches the web.
Computer: The Default to Computer toggle decides whether new sessions start in Computer mode. Turn it off if your team mostly needs quick search answers.
Why it matters: Priority links point web results at sources you trust, so the team gets fewer answers built on random blogs.

Step 5: Invite Teammates
Click Share in the top right. Add people by name or email, or click Copy link. You appear as Owner under "People with access."
Why it matters: Sharing is how one person's research becomes the team's research. Add contributors on purpose, not by default.

Step 6: Maintain Your Project Over Time
Assign one person to review the Files tab every month. Check the box next to an outdated file, click Delete, and upload the current version. There is no replace button, so deleting and re-uploading is the workflow.
Why it matters: Stale files produce stale answers, and stale answers cost you the team's trust.

Real-World Scenario: Competitive Intelligence Project
A product marketing team builds a shared "Competitive Intelligence" Project.
Files uploaded: 2026 Competitor Feature Matrix (CSV), Competitor Q3 Pricing Updates (PDF), and Win-Loss Analysis Transcripts (TXT).
Project instructions:
"You are a competitive intelligence strategist. Use uploaded competitor matrices and win/loss transcripts first. Always contrast competitor offerings directly against our core product capabilities. If pricing or features have changed recently, search the web to verify current public figures and note the publication date."
Question 1: "How does Competitor X's enterprise tier pricing compare to ours?"
What a good answer looks like: It pulls seat pricing from the pricing PDF, notes your advantage on API limits, and cites the document by name.
Question 2: "What are the primary objections prospective buyers mention during sales calls?"
What a good answer looks like: It scans the transcripts, groups the top recurring objections, and quotes the calls directly.
Common Mistakes to Avoid
Sharing edit access with everyone. Broad access leads to cluttered files and overwritten instructions. Keep contributors to designated team leads.
Treating the Files tab as a dumping ground. A 5,000-file limit is not a goal. Uncurated uploads dilute answer quality.
Skipping instructions. Without them, every teammate gets a different answer structure and different citation habits.
Take It Further
Build separate Projects for separate workflows. Sales Enablement, Product Roadmap Research, and HR Policies each get their own files and their own instructions. Focused Projects give sharper answers than one company-wide catch-all.
Pick one high-friction research workflow in your department and build your first Project today.
