How to Set Perplexity Project Permissions Safely
🔍 WiseChecker

How to Set Perplexity Project Permissions Safely

Official documentation checked October 14, 2026.

Give collaborators only the access needed for their work. Reading shared research should not require the ability to delete files or manage other people. Current Perplexity documentation calls these workspaces Projects; older articles and interfaces may say Spaces. This guide covers current Project sharing, not organization administrator roles.

ADVERTISEMENT

Choose the right Project role and audience

The Project guide documents Owner, Can edit, and Can view. Viewers can read shared sessions and files. Editors have broader control over content and configuration, including people. Owner-only settings remain separate.

Use view access for someone who only needs to inspect results. Before granting edit access, decide whether that person should be allowed to modify the workspace and its shared materials. An absent file is not, by itself, evidence that an editor upgrade is needed.

Projects are not publicly queryable. Personal-account sharing is invitation-based; eligible Enterprise accounts also have organization sharing scopes. Do not replace a missing invitation with a publicly shared session containing the same confidential material.

Review and change access deliberately

  1. Open the exact Project and confirm the owner and intended audience. Similar names can conceal a different workspace.
  2. Open Share or the member list at the top right. Record the person’s current access before changing it.
  3. Select or invite the correct account and choose the narrowest role offered for the intended task. Follow the confirmation shown in your interface; do not assume every layout uses an immediate-save dropdown.
  4. Have the recipient open the same Project while signed into their own account. Verify the intended read or edit operation using harmless test content.
  5. If changing or removing access, check whether an organization-wide scope or other applicable membership still grants access. Do not declare revocation complete from one changed dropdown.

For a missing control, ask the Project owner to review access rather than requesting organization Admin as a workaround. Perplexity’s Enterprise roles govern additional capabilities and restrictions. Those organization roles are not interchangeable with Project roles, and a Project invitation does not override an organization policy.

Do not transfer ownership by making someone an invented Project “Admin” and leaving. The current Project guide does not document that as an ownership-transfer procedure. If ownership needs to change, keep the existing owner’s access intact while confirming the supported route with Perplexity support.

ADVERTISEMENT

Check the result without expanding exposure

Agree what success means before testing: a reviewer can open the intended shared file but does not need to replace it; an editor can make an approved change without receiving unrelated organization powers. Test as the recipient, not only as the owner. Never exchange passwords or authentication codes to perform the check.

Connected sources require a separate review. The File Connectors guide distinguishes live source searches, session attachments, and copied Project files. Do not assume that revoking access in a source service retracts every answer or copy already shared in Perplexity. Review the exact object and its sharing scope.

Keep a short record of the Project, affected account, previous role, approved change, and recipient’s result. If access remains wrong, send support a redacted description and relevant account/workspace identifiers through the official support channel. Do not attach confidential files or widen sharing merely to demonstrate the fault.

Removing access prevents intended future use through that access path; it cannot retrieve screenshots or files someone already saved. For a suspected disclosure, involve your organization’s responsible team instead of deleting the Project and losing the evidence needed to understand what happened.

ADVERTISEMENT

Did this guide solve your problem?