Perplexity Projects (formerly Spaces) for marketing teams

#01What's in a Project?

Perplexity's July 2026 post "Spaces are now Projects" explains the rename. Projects are also the shared workspace for Computer, so Automations can use a Project's files, tools and instructions.

#02Which Projects should a marketing team create?

Start with these, then add more only when needed:

Our view: five well-run Projects beat thirty abandoned ones. Archive campaign Projects when the campaign ends.

#03How do you write Project instructions?

Use this structure. It fits comfortably under 8,000 characters:

1. Purpose: what this Project is for (one sentence).
2. Company facts: product, ICP, regions, positioning line, approved claims (link file).
3. Competitors: names + domains (link file).
4. Source rules: prefer / avoid / date window.
5. Output rules: tables first, cite every claim with date, end with "Claims to verify".
6. Style: UK English, plain language, no hype words.
7. Known errors: things Perplexity got wrong before and must not repeat.
8. Never: invent statistics, quote paywalled reports second-hand as fact, include customer names not in the approved list.

#04How should you handle files?

• Name files clearly: 2026-11_competitor-list.csv, approved-claims_v4.pdf.
• Remove old versions. Perplexity may retrieve an outdated fact sheet as readily as the new one.
• Keep sensitive data out unless your plan and policy allow it. Enterprise plans add retention controls. Personal plans need more care.
• Prefer text-heavy files. Clean PDFs, documents and CSVs are easier to search than scanned images.

#05How do connectors and Automations fit in?

Connectors let a Project search live data, such as a shared drive folder of briefs or a Slack channel of win-loss notes. Admins on Enterprise plans control which connectors are allowed.

Computer Automations (see lesson 9) can run on a schedule or be triggered by app events, using the Project's files and instructions. For example: "Every Monday, check Competitors A-D's pricing pages and changelogs and post changes to #competitive-intel." Perplexity's older scheduled-search Tasks are being replaced by Automations.

#06How do you set roles and sharing?

Rules we recommend:

1. Only owners edit instructions. Editors suggest changes in a thread.
2. Agencies get viewer access unless they produce research.
3. Review membership quarterly, or connect SCIM on Enterprise so leavers are removed automatically.

#07What about Brain and memory?

Max and Enterprise Max include Brain, a research-preview memory system for Computer. Perplexity says it builds a private, source-linked context from a user's sessions, connected tools, files and corrections, and that each person's private memory and connected accounts stay scoped to their own access inside shared Projects. Enterprise admins can turn Brain off for the whole organisation, and Perplexity says Enterprise memory isn't used to train models. For marketing teams, the practical advice is to keep the approved facts in Project instructions and files, which you can see and edit, rather than relying on memory you can't inspect.

#08How do you roll Projects out to a team?

A short rollout avoids the "everyone makes their own" problem:

Projects also work in Slack and Microsoft Teams, according to Perplexity's product page, so people can ask questions where they already work. Decide early which channels may connect to which Projects, especially if a Project holds customer notes.

#09Worked example: Ledgerline

Ledgerline is a fictional accounts-payable software company. Details are illustrative.

Ledgerline had 14 Spaces from 2025, most of them abandoned. After the rename, the team audited them.

Walkthrough

1. Listed all Projects and their last activity.
2. Archived the inactive ones after exporting anything useful.
3. Wrote the instruction template and applied it to the five remaining Projects.
4. Consolidated files and deleted old versions.
5. Set roles, with two owners per Project.
6. Created the Monday Automation, then checked its first three runs by hand.

#10Common mistakes

• Instructions that conflict across Projects. Use one template.
• Stale files. Old fact sheets produce old claims.
• Everyone an owner. Someone will rewrite the instructions without telling anyone.
• Personal threads for team research. If it matters, it belongs in a Project.

#11Try it yourself

Create (or clean up) a "Competitive intel" Project. Write version 1 of the instructions with the eight-part structure, upload a competitor list, set roles, and run one teardown prompt from lesson 5. Compare the output with the same prompt outside the Project.

#12Quick quiz

1. What was a Perplexity Project called before July 2026?

Answer: A Space.

2. What is the instructions limit?

Answer: 8,000 characters.

3. Who should be able to edit instructions?

Answer: Owners. Editors can suggest changes.

#13What should you check before the next lesson?

• No more than six active Projects, each with an owner.
• Instructions are versioned and use one template.
• Roles are set, with sales and agencies as viewers.

Previous: SEO and content briefs. Next: Computer and Automations. Or return to the Perplexity for Marketers track. Related: Prompting and source control, Claude for Marketers.

#14Common questions

What happened to Perplexity Spaces? Perplexity renamed Spaces to Projects in July 2026. Existing Spaces became Projects, and Projects add skills, connectors, memory and scheduled work through Computer.

Are Projects private? Projects are private by default. You can invite people as owners, editors or viewers, depending on your plan.

How many files can a Project hold? Perplexity lists up to 10,000 files per Project, 5 GB in total and 100 MB per file. Check your plan, because limits can differ.