diff --git a/admin_manual/contents.rst b/admin_manual/contents.rst index 3a3caa739d0..d1fc1c7bfff 100644 --- a/admin_manual/contents.rst +++ b/admin_manual/contents.rst @@ -52,7 +52,7 @@ Table of contents desktop/index .. toctree:: - :caption: automation + :caption: Automation automation_overview/index file_workflows/index diff --git a/admin_manual/file_workflows/index.rst b/admin_manual/file_workflows/index.rst index c2a7149ead4..4b1cb07a8b9 100644 --- a/admin_manual/file_workflows/index.rst +++ b/admin_manual/file_workflows/index.rst @@ -9,8 +9,8 @@ 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. +provided by the File Access Control, Files Automated Tagging, Files Retention, +Flow Notifications, and Files Versions apps. Additional Flow apps can be found in the `Nextcloud app store `_. @@ -39,3 +39,4 @@ are covered here: automated_tagging retention versioning + notifications diff --git a/admin_manual/file_workflows/notifications.rst b/admin_manual/file_workflows/notifications.rst new file mode 100644 index 00000000000..b76b5f70c01 --- /dev/null +++ b/admin_manual/file_workflows/notifications.rst @@ -0,0 +1,34 @@ +=================== +Send a notification +=================== + +The Flow Notifications app (``flow_notifications``) provides the +**Send a notification** Flow operation. Users can configure it to receive +notifications when events match their conditions. The operation is available +for personal flows, not system-wide flows. + +Prerequisites +------------- + +The Flow Notifications and Notifications apps must be installed and enabled. +Personal flows must also be enabled by the administrator. + +Configuration +------------- + +In personal settings, open Flow and add a **Send a notification** flow. +Choose an event and conditions, and optionally provide a title prefix. +All conditions in a rule group must match for the group to trigger. + +For example, select **File updated** and add a MIME type condition of +``application/pdf``. With the optional title "PDF updated", the flow can +notify the user when another user updates a matching PDF they can access. + +Considerations +-------------- + +Notifications are skipped when the current session user is the flow owner. +For example, a user updating a file in their own session will not receive a +notification through their own flow. + +For the available Flow conditions, see :ref:`available-rules-label`.