Repository navigation
docs(admin): reorganize Flow documentation under Automation - #16009
Open
joshtrichards wants to merge 4 commits into
Open
joshtrichards wants to merge 4 commits into
joshtrichards wants to merge 4 commits into
Conversation
Move the Flow chapter from the Files toctree into the Automation section. Keep its source path unchanged so existing URLs and references continue to work, and retain the `file_workflows` label for cross-references. Seems like a natural follow-up to #15748. Signed-off-by: Josh <josh.t.richards@gmail.com>
Introduce Flow with a proper chapter overview and group its general configuration separately from the documented operations: File Access Control, Files Automated Tagging, and Files Retention. Link to the app store for additional Flow apps. Keep existing document paths and references unchanged. Signed-off-by: Josh <josh.t.richards@gmail.com>
Add a Flow chapter page for the operation provided by the Versions app. Explain how administrators can configure rules to block new versions, including a collaborative tag example and the effect on existing versions. Signed-off-by: Josh <josh.t.richards@gmail.com>
Add link to Flow chapter page for the operation provided by the Versions app. Group the documented operations under a heading that also covers operations provided by general-purpose apps. Signed-off-by: Josh <josh.t.richards@gmail.com>
joshtrichards
marked this pull request as ready for review
November 4, 2026 17:18
nickvergessen
removed their request for review
November 4, 2026 18:10
Contributor
📖 Documentation Preview📄 3 changed documentation pagesLast updated: Wed, 04 Nov 2026 18:56:56 GMT |
hweihwang
approved these changes
Nov 5, 2026
hweihwang
left a comment
hweihwang
left a comment
Contributor
There was a problem hiding this comment.
Looks good from the File access control side.
One suggestion: Block file versioning is only on server master so far (not in stable33 to 35). A .. versionadded:: 36 under the title of versioning.rst would save admins on 35 from looking for it.
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
Summary:
🖼️ Screenshots
✅ Checklist
codespellor similar and addressed any spelling issues