{"resourceId":"perplexity-folder-access-revocation-20260903","versions":[{"version":"external-0d5d51ec3595ea77839e4929a197ac9b5e39132ea564b445bdc19e09626e2e0a","resource":{"id":"perplexity-folder-access-revocation-20260903","title":"Desktop folder permissions require explicit revocation and recovery planning","organization":"Perplexity","sector":"Desktop AI application operations","geography":"Global documentation; institution-specific controls required","publishedAt":"Last modified September 3, 2026","publicationDate":"2026-09-03","eventDate":null,"sourceName":"Perplexity Help Center","sourceLabel":"Vendor operating guidance","sourceUrl":"https://www.perplexity.ai/help-center/en/articles/19800004-work-with-local-files-and-folders","evidenceClass":"standards-guidance","outcomeClass":"cautionary","topics":["knowledge-work","developers-agents","data-security","operating-model"],"finding":"Newly relevant to the September 14 Windows rollout: Perplexity documents persistent folder access, separate revocation in Settings, and potentially unrecoverable deletion. This is general desktop-app guidance, not a Portable Computer security test.","sledRelevance":"Interpretation: applicable to institutional desktop file workflows under consideration; no student or resident-data approval is implied.","evidence":"Operating documentation states selected folders permit reading, creation and changes without a fresh access request each time. No measured failure rate or evaluation sample is given.","architectureImplications":"Interpretation: scope the working directory and test what happens when authorization is removed.","governanceImplications":"Interpretation: maintain an access register and an explicit end-of-pilot revocation step.","securityPrivacyImplications":"Interpretation: distinguish file access authority from where inference runs; they need separate verification.","caveats":"The opened page says last modified September 3, superseding the older July date in search. Guidance is broader than Portable Computer and does not establish sandbox enforcement.","streamIds":["nvidia"],"roles":{"sales":"Sales framing: qualify whether the customer can safely delegate changes to a working folder. Interpretation: ask records owners which files may be edited, who reviews changes and how originals are restored. A suitable engagement is a narrow workflow and recovery assessment using disposable copies. Evaluate reduced handling against review and restoration effort. This guidance cannot establish that the application meets records-retention requirements or that deletion can always be reversed.","engineering":"Engineering framing: test authorization as a lifecycle rather than a single folder selection. Interpretation: create a synthetic workspace, observe allowed edits, deselect the folder, revoke access and retry the same operation. Verify boundary behavior without testing against real sensitive material. Include recovery from an approved destructive action. Document the exact desktop build because this general help page does not prove the controls of every Portable Computer configuration.","delivery":"Delivery framing: make file-access cleanup part of ordinary service operation. Interpretation: give participants a dedicated working folder with recoverable copies and a clear owner for each output. Rehearse how to end access and how to request restoration. Keep the pilot's reviewed outputs separate from records of record until the business owner accepts them. Measure revocation and recovery success as proposed acceptance checks, and document any remaining manual work."},"roleDetails":{"sales":{"customerProblem":"Interpretation: automated file changes need a clear authority and recovery boundary.","stakeholders":["Records owner","Desktop support","Workflow sponsor"],"discoveryQuestions":["Which copied files may the agent change?","Who can authorize deletion and restoration?"],"valueHypothesis":"Interpretation: confined file workflows may reduce handling if review and recovery remain manageable.","potentialEngagement":"Interpretation: folder-permission and restoration workshop with a disposable dataset.","unsupportedClaims":["Compliance with records-retention rules","Guaranteed recoverability of deleted files"]},"engineering":{"fit":"Interpretation: consider file-based tasks with an explicit working directory.","architectureIntegration":"Interpretation: verify the folder grant and revocation path on the intended app build.","prerequisites":["Synthetic directory tree","Known recovery copy","Recorded desktop configuration"],"constraints":["General desktop documentation is not Portable Computer-specific assurance","Data ownership rules still apply"],"security":"Interpretation: test out-of-scope access and revocation without using institutional secrets.","proofOfValue":["Confirm revoked access blocks the next attempted operation","Check deselection separately from revocation","Restore a disposable changed file and verify its contents"]},"delivery":{"work":"Interpretation: document working-folder setup, revocation and restoration.","dependencies":["Recoverable file copies","Records decision owner","Desktop support procedure"],"ownership":"Interpretation: desktop service owner manages access cleanup; records owner accepts outputs.","skillsAdoption":"Interpretation: practice permission removal and approval review.","governanceCheckpoints":["Approve permitted file operations","Review outputs before record adoption","Revoke access at pilot completion"],"acceptanceCriteria":["Every pilot folder has a named owner","Revocation tests pass for every pilot endpoint","Recovery exercise reproduces the original file"],"risks":["Persistent access after task completion","Irrecoverable deletion","Confusing deselection with revocation"]}},"retrievedAt":"2026-09-15T03:00:54Z","enrichedAt":"2026-09-15T03:01:23Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: include folder-selection and revocation exercises in user training, with accessible instructions.","procurementImplications":"Interpretation: require a demonstration of manageable file permissions and recovery before institutional acceptance.","operatingModelImplications":"Interpretation: assign access cleanup and restoration to the endpoint service team.","sourceVerification":{"openedUrl":"https://www.perplexity.ai/help-center/en/articles/19800004-work-with-local-files-and-folders","referenceExcerpt":"To fully remove the app’s access to a folder, go to Settings:","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}