Perplexity Spaces Disappeared? Find Your Workspace and Context

If your Perplexity Spaces disappeared, look under Projects first: Perplexity says Spaces became Projects and existing Spaces migrate automatically. If your work is still missing, check the signed-in account and shared access before assuming deletion. The official migration announcement↗ (opens in a new tab) explains the change.

A separate project record in fenbs can keep your brief, checked findings, and next steps available to another connected assistant while you investigate. It cannot restore a Perplexity workspace or bypass its permissions.

What should I check first when a Space is missing?

1. Look for Projects in the left sidebar and open its menu. Check the project list for the name you remember, rather than looking only for the old Spaces label.
2. Try a saved workspace link from your bookmarks, browser history, or invitation. Note whether it opens, asks for access, or produces an error.
3. Check the email address in account settings. If another device still shows the work, compare its account address before signing out of either device.
4. For shared work, ask the owner to open the same link and check your membership. Send the exact message you see rather than saying only that everything vanished.
5. If the account and access look correct, compare another browser or device and check service status. Save what each test showed before changing anything else.

The current Projects guide↗ (opens in a new tab) documents the sidebar location and sharing controls. Once you find your work, our Perplexity Spaces setup guide covers the separate question of organizing it.

Am I signed into the account that holds the work?

Start with the address shown inside Perplexity, not the profile picture in your browser. Perplexity recommends comparing account emails when sessions appear to be missing↗ (opens in a new tab). That advice helps test the account explanation; it does not establish that a particular missing workspace still exists.

A personal address and a work address are different identities, even if both display your name. Compare the signed-in address with an original invitation or a device where the project remains visible. If they differ, use the intended account and test the saved link again.

Changing the sign-in button alone is not a reliable fix. Perplexity says its email, Google, and Apple sign-in methods↗ (opens in a new tab) reach the same account when the exact email matches, including letter case. Verify the address before creating another account or asking someone to invite a different identity.

Does the owner still see the missing workspace?

Ask the owner to test the original link while you test yours. If they can open the project, have them inspect the member list or Share controls for your intended account. A private-project message is a reason to investigate access, not evidence that the content was deleted.

Projects are private by default. Personal accounts use invitations; Enterprise also offers organization sharing. Where available, use the request-access option or contact the owner. For work tied to an organization, ask its administrator to check your membership and sharing policy rather than assuming every colleague can see the project.

If you can read the project but cannot change it, distinguish that from missing access: view-only access and editing access are different. These controls are described in the Projects guide above. Ask for the access your work requires and keep the workspace private while resolving the issue.

Is this a display problem or a service interruption?

Compare the same saved link using the same account in a second browser or device. Refresh the affected page and, on a phone, check whether an app update is available. Treat these as diagnostic tests: a successful test elsewhere narrows the problem without explaining its cause.

Check Perplexity service status↗ (opens in a new tab) for a relevant incident. An incident can explain loading failures; a clear status page does not prove your account or project is working. If the issue persists, use Help > Contact Support and provide the project link, approximate last successful access, exact error, and browser or app details. Remove unrelated private content from screenshots.

What if someone actually deleted the project?

Ask the owner whether they deliberately deleted it, and distinguish confirmation from a guess based on an empty list. Perplexity’s deletion documentation↗ (opens in a new tab) says deleting a project cannot be undone. Do not plan around an assumed recycle bin or a promised support restoration.

Rebuild only from material you can still access: original source documents, saved deliverables, and notes whose accuracy you can check. Label anything reconstructed from memory. A new workspace with the same name does not demonstrate that the old sources, instructions, or findings have been recovered.

What context should I save while access is unresolved?

Save a short recovery record before troubleshooting turns into several disconnected conversations. Include the project goal, the missing link, which checks passed, who is checking access, and the next action. Keep passwords and sign-in codes out of that record.

• Checked: the owner can open the workspace; my account sees a private-project message.
• Still unknown: whether my invitation used the intended email address.
• Next action: ask the owner to verify membership before rebuilding any research.
• Available context: the approved project brief and original source links, with unverified findings clearly labeled.

Those are example entries, not evidence about your account. In fenbs, project notes and task progress can hold your actual findings separately from the missing workspace. For connection questions rather than workspace recovery, see the Perplexity MCP guide.

How to do this with fenbs

1. Create a free account. fenbs is free for one person, no credit card.
2. Add a project and manually write its brief: the goal, confirmed findings, and source links you still have. Keep missing information explicitly marked as unknown.
3. Add a task for resolving the missing workspace. Record the checks already completed and the next person or action needed; record a person’s confirmed choices in Decisions and rules.
4. Choose a supported AI app from Integrations and connect it through MCP, a standard way for an AI app to use an outside tool. Ask it to read the project context before working and save progress in Where we left off before stopping.

fenbs is not the right fit if your only goal is restoring deleted Perplexity content: it cannot do that or automatically import your Perplexity workspace. It fits when you want a maintained work record across connected assistants. The AI memory guides cover that broader practice; alternatives to Perplexity Spaces covers choosing a different home for the work.