If you find that your teammates can search for answers about a file in a shared space in Perplexity, but can't open the file itself, it's usually not that the space sharing is broken, but that Perplexity's "searchable" and "viewable source files" are not the same level of permissions.
Perplexity's current help center has clearly written this boundary: files synced into a space from connected apps such as Google Drive, SharePoint, OneDrive, Box, Dropbox, etc., can be used by those with access to the space to search and answer; However, if a member does not have file permissions on the original connected app, he may still not be able to open source the file content.
This design is actually very reasonable. Space is responsible for team collaboration and retrieval context, and the original file system is responsible for the underlying permissions. Perplexity doesn't automatically cross the permission boundaries of Drive or SharePoint just because you can ask questions in a space.
So when you see "Can you ask or not", don't rebuild the space first, arrange these layers first:
1. Confirm that the other person has indeed been added to the Space.
2. Then confirm that the other party also has file access permissions in the original cloud disk or document system.
3. If the file has recently been moved, renamed, or unshared, re-sync the Space content.
Many teams mistake this situation for synchronization exceptions, but more often than not, the permission system manages each layer. Space provides a collaboration portal to "answer questions with this data", and whether the original file can be clicked or not is still up to Drive and SharePoint.
If your goal is to allow all members to view the original text directly, syncing files into a space is not enough, so it's best to pair the sharing permissions of the source file as well. This allows team members to search and trace back to the original document.
