From the NVIDIA edition of September 14, 2026
Desktop folder permissions require explicit revocation and recovery planning
Perplexity · Desktop AI application operations · Global documentation; institution-specific controls required
- Publisher
- Perplexity Help Center
- Original publication
- Last modified September 3, 2026
- Source retrieved
- 2026-09-15
What happened
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.
Why it matters
Applicable to institutional desktop file workflows under consideration; no student or resident-data approval is implied.
Evidence and measured results
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.
Limitations and uncertainty
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.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-15; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Interpretation: automated file changes need a clear authority and recovery boundary.
- Stakeholders
- Records owner
- Desktop support
- Workflow sponsor
- Discovery questions
- Which copied files may the agent change?
- Who can authorize deletion and restoration?
- Value hypothesis
- Interpretation: confined file workflows may reduce handling if review and recovery remain manageable.
- Potential engagement
- Interpretation: folder-permission and restoration workshop with a disposable dataset.
- Unsupported claims
- Compliance with records-retention rules
- Guaranteed recoverability of deleted files
Pre-sales engineering
Role takeaway
- Fit
- Interpretation: consider file-based tasks with an explicit working directory.
- Architecture and integration
- 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.
- Proof of value
- Confirm revoked access blocks the next attempted operation
- Check deselection separately from revocation
- Restore a disposable changed file and verify its contents
Delivery
Role takeaway
- 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.
- Skills and adoption
- Interpretation: practice permission removal and approval review.
- Governance checkpoints
- Approve permitted file operations
- Review outputs before record adoption
- Revoke access at pilot completion
- Acceptance criteria
- 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
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Scope the working directory and test what happens when authorization is removed.
Governance
Who approves, reviews and stays accountable for outcomes?
Maintain an access register and an explicit end-of-pilot revocation step.
Security and privacy
What data, permissions and controls need testing?
Distinguish file access authority from where inference runs; they need separate verification.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Include folder-selection and revocation exercises in user training, with accessible instructions.
Procurement
What should contracts, pricing and exit terms secure?
Require a demonstration of manageable file permissions and recovery before institutional acceptance.
Operating model
Which teams own the service once it runs?
Assign access cleanup and restoration to the endpoint service team.
Publication history
- 2026-09-14NVIDIA · Issue 093 resources
Stable resource ID: perplexity-folder-access-revocation-20260903