Add known issue about "Edit locally" for file provider

[i2h3]

See elaborate and technical answer in this GitHub issue comment. This is the concise and user-friendly public documentation.

🖼️ Screenshots

✅ Checklist

• I have built the documentation locally and reviewed the output
• Screenshots are included for visual changes
• I have not moved or renamed pages (or added a redirect if I did)
• I have run codespell or similar and addressed any spelling issues

[Copilot]

Pull request overview

Note

Copilot couldn't run its full agentic review because no GitHub Actions runner was available. Make sure your repository has a runner available to run Copilot's review, or add a copilot-setup-steps.yml file specifying one with the runs-on attribute. See the docs for more details.

Adds a short “known issue” note to the macOS File Provider documentation explaining why the Nextcloud web “Edit locally” action can’t open File Provider–managed files, and offers a Finder-based workaround.

Changes:

• Document limitation of the web “Edit locally” action with macOS File Provider–managed files
• Explain the macOS security restriction behind the limitation
• Provide a user-facing workaround (open from Finder)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

📖 Documentation Preview

🔍 Open preview →

📄 1 changed documentation page

• user_manual/desktop/macosfileprovider.rst

Last updated: Fri, 03 Jul 2026 14:27:35 GMT

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

[Rello]

question on the detail: so this edit-local feature will never work.
is it possible to adopt this to at least a "show in finder" like feature so the location is opened and the user can then open the file on their own? sounds less difficult than potentially navigating 15 folder levels