Skip to content

docs: clarify file access control behavior and limitations - #16036

Open
joshtrichards wants to merge 2 commits into
masterfrom
jtr/admin-flowAccessControl
Open

joshtrichards wants to merge 2 commits into
masterfrom
jtr/admin-flowAccessControl

Conversation

@joshtrichards

@joshtrichards joshtrichards commented Nov 11, 2026 •

Copy link
Copy Markdown
Member

☑️ Resolves

Changes:

  • Explain how rule groups combine, where to configure them, and how folder and collaborative tag conditions work.
  • Document MIME type and file size check limitations, public-link group membership behavior, request-based conditions, and enforcement boundaries.
  • Add an example of blocking the desktop client using its user agent.
  • Clarify that denied files and metadata may remain visible.
  • Tidy up wording throughout and add cross-references to related documentation.

Audited against the implementation. Minor since existing behavior is already buggy: The file-size description assumes nextcloud/server#66509 is merged as proposed.

Follow-up: The existing screenshots, as with many throughout the docs, remain unchanged and still need updating.

🖼️ 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

Explain how rule groups combine, where to configure them, and how folder and collaborative tag conditions work.

Document MIME type and file size check limitations, public-link group membership behavior, request-based conditions, and enforcement boundaries.

Clarify that denied files and metadata may remain visible.

Tidy up wording throughout and add cross-references to related documentation.

Audited against the implementation. The file-size description assumes nextcloud/server#66509 is merged as proposed.

Assisted-by: Copilot:gpt-6.1-terra

Signed-off-by: Josh <josh.t.richards@gmail.com>
@joshtrichards

Copy link
Copy Markdown
Member Author

/backport to stable35

@joshtrichards

Copy link
Copy Markdown
Member Author

/backport to stable34

@joshtrichards

Copy link
Copy Markdown
Member Author

/backport to stable33

@github-actions

github-actions Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

📖 Documentation Preview

🔍 Open preview →

📄 1 changed documentation page

Last updated: Wed, 11 Nov 2026 16:05:56 GMT

Show how to configure a user-agent condition in a file access control flow, and note that clients can spoof their user agent.

Closes #172

Assisted-by: Copilot:gpt-6.1-terra

Signed-off-by: Josh <josh.t.richards@gmail.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update Flow (File Access Control) documentation and screenshots Add an access-control example for blocking specific Nextcloud clients

1 participant