Repository navigation
docs: clarify automated file tagging behavior and downstream actions - #16033
Open
joshtrichards wants to merge 1 commit into
Open
joshtrichards wants to merge 1 commit into
joshtrichards wants to merge 1 commit into
Conversation
Explain rule matching, evaluation triggers, tag permissions, and behavior for existing files and assigned tags. Expand the folder-tagging example and document request-context and storage-root limitations. Clarify that other apps perform downstream actions, with examples and documentation links for retention, access control, and PDF conversion. Signed-off-by: Josh <josh.t.richards@gmail.com>
Contributor
📖 Documentation Preview📄 1 changed documentation pageLast updated: Tue, 10 Nov 2026 16:50:06 GMT |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
☑️ Resolves
Update the automated tagging guide to explain when rules run, how conditions match, and which tags administrators and regular users can assign.
Expand the folder-tagging example and document existing-file behavior, request-context limitations, and storage-root considerations. Replace broad protection guarantees with precise guidance.
Clarify the distinction between assigning tags and performing downstream actions, linking to retention, access control, and PDF Converter documentation.
Related: nextcloud/files_automatedtagging#1811
Known issue: These and other flow related screenshots remain outdated (not addressing that currently in this PR).
🖼️ Screenshots
✅ Checklist
codespellor similar and addressed any spelling issues