Perplexity Project Member Cannot See Files: Safe Access Checks
🔍 WiseChecker

Perplexity Project Member Cannot See Files: Safe Access Checks

Official documentation checked October 14, 2026.

If a collaborator cannot see a file in a Perplexity Space or Project, do not immediately grant editing rights or broaden sharing. Current Project documentation says viewers can read shared Project files. File visibility, source-service access, and editing permissions are different questions.

ADVERTISEMENT

Confirm the exact account, Project, and missing object

Ask the owner and recipient to compare the Project URL, signed-in account, filename, and expected version. Distinguish an absent file listing from an access-denied message, failed preview, or an answer that simply did not cite the file. These observations require different remedies.

Have the recipient open the Project directly in their own signed-in browser. If the whole Project is private to them, the owner should review its Share/member list and provide approved view access. Do not grant organization-wide access to fix one person’s invitation.

Identify where the file was actually added

A file attached to a session is not automatically proof of a persistent Project upload. Perplexity’s upload guide describes attachments as context for that session. Check the actual Project file area and upload result before troubleshooting permissions.

Where the current layout provides Settings, inspect the file listing under Context, or Sources in the newer layout. Ask the authorized uploader to confirm the exact destination. If the material belongs only to a private session, decide whether a separate shared copy is appropriate before adding one. Do not download and redistribute a private document merely because a colleague requests it.

ADVERTISEMENT

Separate a connected source from an imported copy

The connector guide distinguishes a live source query, a session snapshot, and Project imports. First establish which one is missing. Check the member’s own connection and source-file access when the problem concerns a live connector; do not share the uploader’s credentials.

Imported Project files are static copies, not guaranteed continuous mirrors. A source rename or deletion does not automatically remove the Project copy. Avoid assuming that a source permission change proves the imported content is inaccessible. Conversely, permission to view a Project is not proof of permission to open every original cloud-storage link. The documentation describes multiple access paths; test the specific file and action rather than promising universal inheritance.

Check organization policy and upload errors narrowly

On Enterprise, an administrator can inspect the relevant roles and permissions. Downloading files, attaching files to sessions, managing Project files, and controlling connectors are separate capabilities. Ask for the specific intended operation, not a blanket Admin or edit upgrade.

Preserve any upload error and compare it with the limits for that destination. Do not delete existing research to test whether capacity is the cause. If a harmless test file works but the real file does not, investigate that file’s upload, format, source, and access; the test does not establish that every file is supported or fully analyzed.

ADVERTISEMENT

Retest and escalate without losing data

After an approved narrow change, reload the Project and retry the exact action as the affected member. Compare another supported browser only if the account and destination are unchanged. Do not erase all browser data, remove and recreate the Project, or re-upload a sensitive library as a first response.

Record whether the file is absent, visible but unreadable, or readable but omitted from an answer. A missing citation is not an access test, and an old answer is not proof of current file access. Use non-sensitive test content where possible.

If the discrepancy persists, follow the official bug-report route with the time, client version, affected account, Project identifier, redacted error, and reproducible steps. Keep the original file and access settings intact while awaiting a supported resolution. There is no verified rule that all earlier files are hidden from newly invited viewers.

ADVERTISEMENT

Did this guide solve your problem?