docs(admin): reorganize Flow documentation under Automation

admin_manual/contents.rst

@@ -35,7 +35,6 @@ Table of contents
     :caption: Files
 
     configuration_files/index
-    file_workflows/index
     configuration_mimetypes/index
 
 .. toctree::
@@ -56,6 +55,7 @@ Table of contents
     :caption: automation
 
     automation_overview/index
+    file_workflows/index
     webhook_listeners/index
     webhook_listeners/budibase_workflows
     windmill_workflows/index

admin_manual/file_workflows/index.rst

@@ -4,11 +4,38 @@
 Flow
 ====
 
+Flow provides rule-based automation in Nextcloud. Administrators can define
+system-wide flows, while users can define personal flows (unless disabled
+by the administrator).
+
+Apps can provide additional Flow operations. This chapter covers operations
+provided by File Access Control, Files Automated Tagging, Files Retention
+and the Versions app.
+
+Additional Flow apps can be found in the `Nextcloud app store
+<https://apps.nextcloud.com/>`_.
+
+General configuration
+---------------------
+
+The following settings apply to Flow itself rather than to an individual Flow app
+/ operation.
 
 .. toctree::
     :maxdepth: 2
 
     configuration
+
+Operations
+----------
+
+Each app provides its own functionality and configuration. The following Flow operations
+are covered here:
+
+.. toctree::
+    :maxdepth: 2
+
     access_control
     automated_tagging
     retention
+    versioning

admin_manual/file_workflows/versioning.rst

@@ -0,0 +1,34 @@
+=====================
+Block file versioning
+=====================
+
+The Versions app (``files_versions``) provides the **Block file versioning**
+Flow operation. Administrators can use it to prevent new file versions from
+being created when a file matches specified rules. The operation is available
+for system-wide flows, not personal flows.
+
+Configuration
+-------------
+
+In Administration settings, open Flow and add a **Block file versioning**
+flow. Add at least one rule specifying which files should not be versioned.
+The operation is evaluated when a new version would otherwise be created.
+
+For example, add a **File collaborative tag** rule to block version creation
+for files with a particular tag. The rule also matches files in folders with
+that tag; see :ref:`available-rules-label` for details.
+
+Effects
+-------
+
+When a flow matches, the Versions app skips creating the new version. This
+does not block the file change or delete existing versions. Existing versions
+remain subject to the normal version expiration rules.
+
+.. warning::
+
+   Changes made without creating a version cannot be recovered through that
+   skipped version.
+
+For general version retention and expiration settings, see
+:doc:`../configuration_files/file_versioning`.